MCP tool reference (generated)
Every tool GoodQA's remote MCP server (POST /v1/mcp) can register, grouped as MCP tools groups
them: the gate that registers the group, then per tool the exact description your MCP client is given, its
parameters, an example call and related tools. A group whose gate is off for your key's org is simply missing from
your tool list; never reach it through call_api (the route answers 404 too). Feature guides:
docs/features. Regenerate: pnpm --filter @bugtracker/api exec tsx scripts/export-mcp-tool-reference.ts.
Remote tools described here: 479 in 69 groups. Stdio-only tools are listed at the end.
Groups
| Group | Registered when | Tools |
|---|---|---|
remote-core | always (any key; ticket file tools require TICKET_FILES_ENABLED, default ON) | 91 |
remote-network | always; no registration feature flag; authenticated organization/project routes enforce permissions, connection task and agent grants, owner acceptance and revocation | 10 |
remote-feature-card-media | Live platform grant: inventory sees 1, media sees 3; signed-in platform admin sees 5. Grant/revoke always human-only. Agent kill switch featureCards.agentMedia | 5 |
remote-work-coordinator | workCoordinator.enabled (default on), explicit work scope, current principal grants; write scope on mutations | 13 |
remote-image-studio | IMAGE_STUDIO_ENABLED (on by default); org ai.enabled for listing; project ai:use enforced on every call | 7 |
remote-roadmap | whatsNew.roadmapEnabled + WHATS_NEW_ROADMAP_ENABLED (both on by default); org-bound non-runner keys with an explicit issues grant; suggestions also need roadmap_suggestions + write. Reads curated items; drafts create no ticket (roadmap votes) | 4 |
remote-command-center | Platform commandCenter.enabled and org entitlement on | 1 |
remote-agent-queue | platform agentQueue.enabled (on by default); org bot keys read and enqueue, people reorder | 3 |
remote-scheduling | org scheduling.enabled + crm.api.enabled; runner keys refused | 6 |
remote-imports | imports.enabled on by default, CRM flags, admin, never runner | 3 |
remote-form-crm | org crm.formMapping, forms.enabled, crm.enabled, crm.v2.records, crm.api.enabled (on by default); org admin and form access | 2 |
remote-crm-records | org: crm.api.enabled + crm.v2.records (on by default) | 10 |
remote-crm-reports | platform: crm.reports.enabled (default off) + org: crm.reports and crm.api.enabled | 2 |
remote-crm-lifecycles | org: crm.api.enabled + crm.v2.lifecycles (on by default) | 7 |
remote-crm-relationships | org: crm.api.enabled + crm.v2.relationships (on by default) | 11 |
remote-crm-webhooks | org: crm.api.enabled + crm.v2.webhooks (on by default) | 1 |
remote-decisions | platform: governance.decisions | 3 |
remote-issue-proposals | platform: chat.issueProposals (on by default); chat family | 2 |
remote-chat-questions | platform: chat.questions (on by default) | 2 |
remote-chat-progress | deployment: CHAT_UX_ENABLED (on by default); status writes enforce the caller's chat scope and conversation membership | 1 |
remote-chat-lines | platform: chat.lines (off by default) | 2 |
remote-secret-requests | platform: vault.requests + org: vaultRequests.enabled (both on by default) | 2 |
remote-attachment-sharing | platform: attachments.sharing (on by default) | 4 |
remote-custom-data | deployment configured (CUSTOM_DATA_CLUSTER_URL) + org: customData.enabled (the org flag defaults ON, but no tools exist until the deployment is configured); key names data, no persona | 12 |
remote-agent-knowledge | org: agentKnowledge.enabled (on by default; and the status route says this key gets them) | 5 |
remote-memory-service | MEMORY_SERVICE_ENABLED (on by default), explicit memory family and live org/project permissions; human sessions approve | 5 |
remote-context-memory | CONTEXT_MEMORY_ENABLED (on by default), successful live scoped read and context_memory family; human sessions approve | 3 |
remote-project-memory | platform and org: projectMemory.enabled (both on by default); explicit project_memory family plus read and mcp; writes also need write and project:share_agent_context; no runner, user-scoped key or delegated user token | 6 |
remote-coordinator | org: coordinator.bootstrap (on by default since 2026-10-04, an org override turns it off; and the coordinator status route says this key gets them: a standard key naming no family, or naming issues, decisions, agent_knowledge and agent_memory) | 2 |
remote-outreach-daily | OUTREACH_DAILY_PLAYBOOK_ENABLED, outreach/API and CRM/API entitlements; live CRM/project access; no runners or scoped keys | 3 |
remote-outreach | org: outreach.enabled + outreach.api.enabled (on by default); never a runner key | 18 |
remote-outreach-deliver | the two outreach flags + at least one of outreach.gmail, outreach.outlook, outreach.zoho (its provider enum lists only those; all on by default) | 1 |
remote-outreach-byo | the two outreach flags + outreach.byo (on by default) | 4 |
remote-outreach-pipeline | deployment: OUTREACH_PIPELINE_VIEW_ENABLED (default OFF) + org: outreach.enabled, outreach.api.enabled, outreach.pipelineView + CRM read permission; no runners | 2 |
remote-outreach-manual | OUTREACH_MANUAL_LOG_ENABLED (default ON), outreach flags + outreach.manualLog + sequences + CRM | 1 |
remote-outreach-queue | the two outreach flags + outreach.queue (on by default); never a runner or user-scoped key | 5 |
remote-agent-launch | platform: agents.launch on for the key's org (on by default, all; see the agent daemon guide); key names agent_launch; never a runner or user-scoped key. Read and cancel only: no tool launches a run | 4 |
remote-notes-to-self | NOTES_TO_SELF_ENABLED (on by default) + the key is the user's OWN personal key (minted by them, scoped to them, standard, no persona); every other key's list is unchanged | 3 |
remote-my-work | Platform myWork.enabled and org entitlement on | 1 |
remote-usage | platform: usage.metering (on by default); every organization key lists the tools, while routes enforce the key's own org and org-admin authority; usage_model_record additionally requires usage:write; never a runner key (nor a persona key to record) | 3 |
remote-changes | platform: changes.digest (on by default) | 2 |
remote-discovery | deployment: AGENT_DISCOVERY_ENABLED (on by default; any key) | 2 |
remote-agent-ops | platform: mcp.agentOps (on by default); every tool calls existing routes with your key, the persona tools need a persona key | 10 |
remote-agent-ops-memory | platform: mcp.agentOps + org: agentKnowledge.enabled (both on by default); key family agent_knowledge | 1 |
remote-agent-ops-lanes | platform: mcp.agentOps + org: coordinator.bootstrap (both on by default); the coordinator route decides the key | 1 |
remote-agent-ops-crm | platform: mcp.agentOps + org: crm.api.enabled + crm.v2.records (all on by default); never a runner key | 1 |
remote-agent-ops-hosting | platform: mcp.agentOps + managed hosting covering the key's org (agents.managedHosting and agents.launch, both all, on by default); key names agent_launch, org admin, never a runner key | 2 |
remote-agent-chat | platform: agentChat.enabled (off by default) + persona key only: the key wears a live persona, is not user-scoped and names chat or no family (the persona status route decides); every other key's list is unchanged. docs/design/AGENT-CHAT.md | 12 |
remote-agent-chat-delivery | platform: agentChat.reliableDelivery (off by default, dark) on top of remote-agent-chat, persona key only: registered only while GET /v1/persona/agent-chat/status answers reliableDelivery: true. docs/agent-chat-reliability.md | 6 |
remote-user-tokens | a USER-TOKEN (gqut_) MCP session only, while the platform setting userTokens.enabled holds (default off since review round 2); never an org API key, so no key's list changes. create_org is listed only for the bootstrap-email rollout while userTokens.orgAdmin is on; add_org_member, set_org_member_role and remove_org_member use live org authority, with a reasoned platform-admin ownership override supported by set_org_member_role; user_tokens_create is omitted while human-only minting is on. Each tool calls the same REST route with the token, so its abilities, mint-chain rules and approval switch apply (docs/design/USER-TOKENS.md) | 8 |
remote-browser-control | machines.enabled + machines.browserControl (off by default) + signed-in org owner consent; Machines key family and grant | 38 |
remote-agent-browsers | agentBrowsers.enabled actions on by default; stop/status remain registered while disabled; organization lease grants required for actions | 15 |
remote-user-token-session-actions | A human-issued user token with an explicit session ability, platform userTokens.sessionActions ON (default OFF), and an org owner opt-in inside its allow-list. REST rechecks grants, expiry, roles and approval on every call. With this flag on user_tokens_create is absent; tokens can never mint tokens. | 1 |
remote-machines | platform: machines.enabled on for the key's org (off by default: off, or all, or a list of org ids; an operator switch) + the key reaches the machines family (names it, or a personal standard key naming no family); never a runner key. docs/design/GOODQA-MACHINES.md | 46 |
remote-workers | machines.enabled on for the key's org + machines family; never runner or user token. Quotes and spending require owner-approved vault pools and designated keys; spawning requires a standing allowance or signed-in owner approval of the exact quote. Commands retain machine grants and signed results. | 5 |
remote-machine-enroll | a USER-TOKEN (gqut_) MCP session only, while machines.enabled is on for some org and the token holds machines; never an org API key. Machine tokens and enrollment status, never machine use: minting needs tokens.create_other_keys and asks first when the token requires approval (docs/design/machines-fullcontrol/ENROLLMENT.md) | 4 |
remote-telephony | org: telephony.enabled (OFF on every plan); org admin and orgs read scope; never a runner or user-token session; read only | 1 |
remote-escalation | org: escalation.enabled (off on every plan: real phone spend, can wake people; a platform admin turns it on per org) | 5 |
remote-routines | platform: routines.enabled for the org (off by default); org/project access; responses require the named person | 3 |
remote-content-work | deployment: CONTENT_ENGAGEMENTS_ENABLED on by default; current CMS org/project authority; drafts and edits never approve or publish | 5 |
remote-automations | org: automations.enabled, crm.enabled and crm.api.enabled (all on by default); never a runner key. Workflows have no mail sending action | 5 |
remote-work-dashboard | platform: workDashboard.enabled + org: workDashboard (both on by default); an org key must carry the explicit work_dashboard scope, a user token the issues ability; never a runner or user-scoped key. Read only | 1 |
remote-blueprints | blueprints.enabled for the org; admin; apply requires a recorded person approval | 4 |
remote-org-builder | org_builder.drafter and blueprints.enabled for the org; admin; apply requires a recorded person approval, and an agent has no approve tool | 4 |
remote-ahrefs | mcp.agentOps (on by default); org member with marketing scope, current owner/admin Ahrefs consent; finder additionally requires project access and CRM create | 12 |
remote-product-expert | platform: mcp.agentOps + mcp.productExpert (both on by default); read only, any key: search over the embedded GoodQA product pack (product expert) | 8 |
remote-harness-contract | platform: harness.contract covering the key's org (off by default) + a valid x-goodqa-run-id request header. Typed result for this run; writes no data | 1 |
remote-agent-gaps | deployment: AGENT_GAPS_ENABLED (off by default). Each tool calls the existing chat route with the caller's key; the route decides membership and permissions | 3 |
remote-agent-ops-handoff | platform: mcp.agentOps + browserHandoff.enabled covering the key's org (off by default, dark: off, all or a list of org ids; an operator switch); needs a key with a persona. The link goes to a person by DM, never to the agent. docs/design/browser-handoff.md | 3 |
remote-core
Read remote-core tools and parameters
remote-network
Read remote-network tools and parameters
remote-feature-card-media
Read remote-feature-card-media tools and parameters
remote-work-coordinator
Read remote-work-coordinator tools and parameters
remote-image-studio
Read remote-image-studio tools and parameters
remote-roadmap
Read remote-roadmap tools and parameters
remote-command-center
Read remote-command-center tools and parameters
remote-agent-queue
Read remote-agent-queue tools and parameters
remote-scheduling
Read remote-scheduling tools and parameters
remote-imports
Read remote-imports tools and parameters
remote-form-crm
Read remote-form-crm tools and parameters
remote-crm-records
Read remote-crm-records tools and parameters
remote-crm-reports
Read remote-crm-reports tools and parameters
remote-crm-lifecycles
Read remote-crm-lifecycles tools and parameters
remote-crm-relationships
Read remote-crm-relationships tools and parameters
remote-crm-webhooks
Read remote-crm-webhooks tools and parameters
remote-decisions
Read remote-decisions tools and parameters
remote-issue-proposals
Read remote-issue-proposals tools and parameters
remote-chat-questions
Read remote-chat-questions tools and parameters
remote-chat-progress
Read remote-chat-progress tools and parameters
remote-chat-lines
Read remote-chat-lines tools and parameters
remote-secret-requests
Read remote-secret-requests tools and parameters
remote-attachment-sharing
Read remote-attachment-sharing tools and parameters
remote-custom-data
Read remote-custom-data tools and parameters
remote-agent-knowledge
Read remote-agent-knowledge tools and parameters
remote-memory-service
Read remote-memory-service tools and parameters
remote-context-memory
Read remote-context-memory tools and parameters
remote-project-memory
Read remote-project-memory tools and parameters
remote-coordinator
Read remote-coordinator tools and parameters
remote-outreach-daily
Read remote-outreach-daily tools and parameters
remote-outreach
Read remote-outreach tools and parameters
remote-outreach-deliver
Read remote-outreach-deliver tools and parameters
remote-outreach-byo
Read remote-outreach-byo tools and parameters
remote-outreach-pipeline
Read remote-outreach-pipeline tools and parameters
remote-outreach-manual
Read remote-outreach-manual tools and parameters
remote-outreach-queue
Read remote-outreach-queue tools and parameters
remote-agent-launch
Read remote-agent-launch tools and parameters
remote-notes-to-self
Read remote-notes-to-self tools and parameters
remote-my-work
Read remote-my-work tools and parameters
remote-usage
Read remote-usage tools and parameters
remote-changes
Read remote-changes tools and parameters
remote-discovery
Read remote-discovery tools and parameters
remote-agent-ops
Read remote-agent-ops tools and parameters
remote-agent-ops-memory
Read remote-agent-ops-memory tools and parameters
remote-agent-ops-lanes
Read remote-agent-ops-lanes tools and parameters
remote-agent-ops-crm
Read remote-agent-ops-crm tools and parameters
remote-agent-ops-hosting
Read remote-agent-ops-hosting tools and parameters
remote-agent-chat
Read remote-agent-chat tools and parameters
remote-agent-chat-delivery
Read remote-agent-chat-delivery tools and parameters
remote-user-tokens
Read remote-user-tokens tools and parameters
remote-browser-control
Read remote-browser-control tools and parameters
remote-agent-browsers
Read remote-agent-browsers tools and parameters
remote-user-token-session-actions
Read remote-user-token-session-actions tools and parameters
remote-machines
Read remote-machines tools and parameters
remote-workers
Read remote-workers tools and parameters
remote-machine-enroll
Read remote-machine-enroll tools and parameters
remote-telephony
Read remote-telephony tools and parameters
remote-escalation
Read remote-escalation tools and parameters
remote-routines
Read remote-routines tools and parameters
remote-content-work
Read remote-content-work tools and parameters
remote-automations
Read remote-automations tools and parameters
remote-work-dashboard
Read remote-work-dashboard tools and parameters
remote-blueprints
Read remote-blueprints tools and parameters
remote-org-builder
Read remote-org-builder tools and parameters
remote-ahrefs
Read remote-ahrefs tools and parameters
remote-product-expert
Read remote-product-expert tools and parameters
remote-harness-contract
Read remote-harness-contract tools and parameters
remote-agent-gaps
Read remote-agent-gaps tools and parameters
remote-agent-ops-handoff
Read remote-agent-ops-handoff tools and parameters