Resources

The BoltOps MCP server

Agents connect over the Model Context Protocol. One endpoint covers Bolts, intent documents, comments, stages, and branches. Setup for Claude Code, Cursor, and Claude.ai is in the MCP guide.

Endpoint

Where to connect

JSON-RPC over Streamable HTTP. Authenticate with a bearer token on every request.

POST https://www.boltopsbyelevate.com/api/mcp
Authentication

Two credentials, one server

API token

Create a bops_… token under Settings → API Tokens (owners and admins). Send it as Authorization: Bearer. This is the header Claude Code and Cursor use. The plaintext is shown once.

OAuth 2.1

Claude.ai and other custom connectors paste the endpoint URL. A 401 points them at the OAuth discovery documents, and they come back with a bops_at_… access token. Issuing a token or an OAuth grant works on every plan.

Scopes

What a credential can do

tools/list is filtered to the scopes on the credential. Plan filtering of that list applies only in enforce mode. In warn or off mode the list shows every tool those scopes allow. Service Desk tools (desk:read, desk:write) follow an active or trialing Service Desk module, not the plan table. The MCP guide has the client setup.

ScopeAllowsTools
readRead Bolts, intent documents, projects, comments and Bolt context.7
writeCreate and update intent documents and Bolts, post comments, log activity.6
stageAdvance a Bolt through its lifecycle stages.1
branchSet a Bolt's branch name and link it to a git connection.1
desk:readRead Service Desk tickets, companies, SLA state and knowledge.6
desk:writeCreate and update Service Desk tickets, reply, add notes and link Bolts.9
PlanScopes
Starterread
Growthread, write, stage, branch
Proread, write, stage, branch
Studioread, write, stage, branch
Enterpriseread, write, stage, branch

An active 14-day trial of Growth, Pro, or Studio includes that plan's scopes. Growth, Pro, Studio, and Enterprise are not denied read, write, stage, or branch. Requests are rate limited per organization. Studio and Enterprise have higher limits. See pricing for plans.

Tools

Registered tools

Descriptions and arguments are in the MCP guide. Names come from the server registry.

ToolScope
boltops_whoamiread
boltops_list_boltsread
boltops_get_boltread
boltops_get_bolt_contextread
boltops_list_projectsread
boltops_get_intent_documentread
boltops_list_commentsread
boltops_create_intent_documentwrite
boltops_update_intent_documentwrite
boltops_create_boltwrite
boltops_update_boltwrite
boltops_add_commentwrite
boltops_log_activitywrite
boltops_advance_bolt_stagestage
boltops_set_bolt_branchbranch
boltops_desk_list_ticketsdesk:read
boltops_desk_get_ticketdesk:read
boltops_desk_create_ticketdesk:write
boltops_desk_replydesk:write
boltops_desk_add_internal_notedesk:write
boltops_desk_update_ticketdesk:write
boltops_desk_link_boltdesk:write
boltops_desk_search_knowledgedesk:read
boltops_desk_create_article_draftdesk:write
boltops_desk_list_companiesdesk:read
boltops_desk_get_companydesk:read
boltops_desk_get_sla_statusdesk:read
boltops_desk_run_lookupdesk:write
boltops_desk_log_timedesk:write
boltops_desk_hand_offdesk:write

Open the MCP guide for Claude Code, Cursor, and OAuth connector setup.

Ready to ship at Bolt speed?

Join engineering teams that have replaced sprint ceremonies with AI-orchestrated workflows.