Build solutions, not workarounds.
What do you want BugHerd and Qase to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What BugHerd can start in Qase
When Comment Created in BugHerd
then Add defect in Qase
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with BugHerd and Qase
Triggers and actions 4 triggers · 43 actions
- Comment Created
Triggers when a comment is created
- Project Created
Triggers when a project is created.
- Task Created
Triggers only when a task is created
- Task Created or Updated
Triggers when a task is created or updated.
- Add a Comment to a Task
Adds a Comment to a Task
- Add an Attachment to a Task
Adds an Attachment to a Task
- Create a New Task
Creates a New Task.
- Create a Project
Creates a Project.
- Delete Attachment
Permanently deletes an attachment from a BugHerd task.
- Delete Project
Permanently deletes a BugHerd project and all of its associated data.
- Delete Task
Delete a task from a project.
- Find Task by External Id
Returns the tasks in a BugHerd project whose external ID matches the one you supply.
- Get Project
Retrieve a single project by id.
- Get Task
Returns full details for a single task within a BugHerd project.
- List Attachments
Return all attachments on a task.
- List Comments
Returns all comments on a BugHerd task.
- List Projects
Lists all projects in your BugHerd organization, including both active and inactive projects.
- List Tasks
Return all tasks in a project.
- Update a Task
Updates one or more fields on an existing BugHerd task. Only the fields you fill in are changed.
- Update Project
Updates a BugHerd project's settings. Only the fields you fill in are changed.
- Add defect
Adds a new defect to a Qase project.
- Add milestone
Creates a milestone in a Qase project.
- Add project
Create a new project.
- Add run
Create a new test run in a project.
- Add test case
Create a new test case in a project.
- Add test run result
Create a result for a test run.
- Complete run
Mark a specific test run as completed.
- Delete project
Delete a project by code.
- Delete run
Delete a test run by id.
- Delete test case
Delete a test case by id.
- Find entities by QQL
Searches Qase test cases, defects, runs, results, plans or requirements with a Qase Query Language (QQL) expression.
- Get defect
Get a specific defect by id.
- Get project
Get a project by its code.
- Get run
Retrieves a specific test run in a Qase project, including its status, statistics, environment, milestone, tags and custom field values.
- Get test case
Get a specific test case by id.
- Get test run result
Get a test run result by hash code.
- List defects
Returns all defects in a Qase project, optionally filtered by status.
- List milestones
Get all milestones in a project.
- List projects
Lists every project available to the connected Qase account.
- List runs
Get all test runs in a project.
- List test cases
Get all test cases in a project.
- List test run results
Get all results for a project's test runs.
- Resolve defect
Marks a specific defect in a Qase project as resolved.
- Update defect
Update an existing defect.
- Update run
Update a specific test run.
- Update test case
Updates an existing test case in a Qase project. Only the fields you fill in are changed.
- Update test run result
Update a test run result.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from BugHerd
BugHerd to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BugHerd to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BugHerd to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BugHerd to Google SheetsGoogle Sheets
BugHerd to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BugHerd to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Qase
Questions
BugHerd and Qase, answered
What can start an automation from BugHerd?
Any of BugHerd's 4 triggers in the catalog, including Comment Created, Project Created, Task Created and Task Created or Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Qase when something happens in BugHerd?
Any of Qase's 27 actions, including Update defect, Update run, Update test case and Update test run result. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qase to BugHerd?
Qase has no triggers in the catalog today, so automations start in BugHerd. If you need the other direction, ask: your agent reads Qase's API documentation and adds it.
Do I have to build a connector for BugHerd or Qase?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.