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.
JSON-RPC over Streamable HTTP. Authenticate with a bearer token on every request.
POST https://www.boltopsbyelevate.com/api/mcp
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.
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.
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.
| Scope | Allows | Tools |
|---|---|---|
read | Read Bolts, intent documents, projects, comments and Bolt context. | 7 |
write | Create and update intent documents and Bolts, post comments, log activity. | 6 |
stage | Advance a Bolt through its lifecycle stages. | 1 |
branch | Set a Bolt's branch name and link it to a git connection. | 1 |
desk:read | Read Service Desk tickets, companies, SLA state and knowledge. | 6 |
desk:write | Create and update Service Desk tickets, reply, add notes and link Bolts. | 9 |
| Plan | Scopes |
|---|---|
| Starter | read |
| Growth | read, write, stage, branch |
| Pro | read, write, stage, branch |
| Studio | read, write, stage, branch |
| Enterprise | read, 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.
Descriptions and arguments are in the MCP guide. Names come from the server registry.
| Tool | Scope |
|---|---|
boltops_whoami | read |
boltops_list_bolts | read |
boltops_get_bolt | read |
boltops_get_bolt_context | read |
boltops_list_projects | read |
boltops_get_intent_document | read |
boltops_list_comments | read |
boltops_create_intent_document | write |
boltops_update_intent_document | write |
boltops_create_bolt | write |
boltops_update_bolt | write |
boltops_add_comment | write |
boltops_log_activity | write |
boltops_advance_bolt_stage | stage |
boltops_set_bolt_branch | branch |
boltops_desk_list_tickets | desk:read |
boltops_desk_get_ticket | desk:read |
boltops_desk_create_ticket | desk:write |
boltops_desk_reply | desk:write |
boltops_desk_add_internal_note | desk:write |
boltops_desk_update_ticket | desk:write |
boltops_desk_link_bolt | desk:write |
boltops_desk_search_knowledge | desk:read |
boltops_desk_create_article_draft | desk:write |
boltops_desk_list_companies | desk:read |
boltops_desk_get_company | desk:read |
boltops_desk_get_sla_status | desk:read |
boltops_desk_run_lookup | desk:write |
boltops_desk_log_time | desk:write |
boltops_desk_hand_off | desk:write |
Open the MCP guide for Claude Code, Cursor, and OAuth connector setup.
Join engineering teams that have replaced sprint ceremonies with AI-orchestrated workflows.