BugHerd MCP integration for AI agents.
Connect AI agents to BugHerd through 14 structured actions, including get project, create attachment from url, and show organization. Review authentication…
- ACTION CONTRACTS
- 14
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BugHerd integration exposes
The BugHerd Agent App exposes 14 provider-backed actions for developer tools and productivity work. Its current contract lets an authorized agent retrieve full details for a bugherd project, create a bugherd task attachment from a publicly accessible file url, and retrieve top-level details about the authenticated bugherd organization. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BugHerd account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BugHerd capabilities.
Showing 12 of 14 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_projectREADRetrieve full details for a BugHerd project.
INPUTS: project_id
create_attachment_from_urlWRITECreate a BugHerd task attachment from a publicly accessible file URL.
INPUTS: project_id / task_id / file_name / url
show_organizationREVIEWRetrieve top-level details about the authenticated BugHerd organization.
create_commentWRITECreate a comment on a BugHerd task.
INPUTS: project_id / task_id / text / user_id / email
create_projectWRITECreate a BugHerd project with the required project name and website URL.
INPUTS: name / devurl / is_active / is_public / guests_see_guests
create_taskWRITECreate a BugHerd task in a project.
INPUTS: project_id / description / priority / status / requester_id
get_taskREADRetrieve a BugHerd task by project ID and global task ID.
INPUTS: project_id / task_id
list_active_projectsREADList active BugHerd projects in the organization.
INPUTS: page
list_attachmentsREADList file attachments on a BugHerd task.
INPUTS: project_id / task_id
list_commentsREADList comments on a BugHerd task.
INPUTS: project_id / task_id
list_project_tasksREADList BugHerd tasks for a project with optional server-side filters.
INPUTS: project_id / updated_since / created_since / status / priority
list_projectsREADList all BugHerd projects in the organization.
INPUTS: page
INPUT CONTRACTS
Know what the action needs before it runs.
get_project
project_idREQUIRED- The BugHerd project identifier.
create_attachment_from_url
project_idREQUIRED- The BugHerd project identifier.
task_idREQUIRED- The globally unique BugHerd task identifier.
file_nameREQUIRED- The file name to store with the attachment.
urlREQUIRED- The publicly accessible URL that BugHerd should download and attach.
create_comment
project_idREQUIRED- The BugHerd project identifier.
task_idREQUIRED- The globally unique BugHerd task identifier.
textREQUIRED- The comment text.
user_idOPTIONAL- The BugHerd user identifier for the commenter.
emailOPTIONAL- The commenter email address. BugHerd looks up the user by email.
create_project
nameREQUIRED- The BugHerd project name.
devurlREQUIRED- The primary website URL for the BugHerd project.
is_activeOPTIONAL- Whether the BugHerd project is active.
is_publicOPTIONAL- Whether public feedback is enabled for the BugHerd project.
guests_see_guestsOPTIONAL- Whether project guests can see other guests' feedback.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Project
Retrieve full details for a BugHerd project. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_projectControl Create Attachment From Url
Create a BugHerd task attachment from a publicly accessible file URL. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_attachment_from_urlVerify with Get Task
Retrieve a BugHerd task by project ID and global task ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_taskSAFETY BOUNDARY
Operate BugHerd with explicit limits
- Authorize BugHerd with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BugHerd rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BugHerd task completed successfully.
CONNECTION MODEL
API key
BugHerd API key used as the Basic Auth username with x as the password. Find it under Settings > General in your BugHerd account: https://www.bugherd.com/settings/general.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BugHerd.