The Model Context Protocol server lets Claude, Cursor, and other MCP clients read and update Bolts in your workspace. One HTTP endpoint, two ways to authenticate, and the tools listed below.
A Bolt is a short cycle of work: intent, generate, verify, review, iterate, ship. The MCP server exposes that workflow so an agent can find a Bolt, read its intent document, and write progress back. The protocol is JSON-RPC over Streamable HTTP. Responses are JSON.
POST https://www.boltopsbyelevate.com/api/mcp
Send one JSON-RPC message per request with an Authorization: Bearer header. Opening the URL in a browser returns 405; the link in that response points here.
Clients that can store a header use an API token (bops_…). Clients that cannot, including Claude.ai custom connectors, use OAuth 2.1 (bops_at_…). Both reach the same tools. You can create either credential on any plan.
In BoltOps, open Settings → API Tokens. Owners and admins can create a token, choose its scopes, and copy it once. BoltOps stores only a hash. Put the token in an environment variable rather than in a committed file:
export BOLTOPS_TOKEN='bops_...'
claude mcp add --transport http boltops https://www.boltopsbyelevate.com/api/mcp \ --header "Authorization: Bearer $BOLTOPS_TOKEN"
Ask the client to call boltops_whoami. The result is the organization, the person the token acts as, and the scopes on the token.
Omit the header. Claude Code uses HTTP transport, receives the 401 challenge, and runs OAuth discovery.
claude mcp add --transport http boltops https://www.boltopsbyelevate.com/api/mcp
Add a remote server in .cursor/mcp.json (or Cursor Settings → MCP) with the bearer token:
{
"mcpServers": {
"boltops": {
"url": "https://www.boltopsbyelevate.com/api/mcp",
"headers": {
"Authorization": "Bearer bops_..."
}
}
}
}Add a custom connector and paste https://www.boltopsbyelevate.com/api/mcp. The server answers unauthenticated calls with 401 and a WWW-Authenticate header whose resource_metadata URL is https://www.boltopsbyelevate.com/.well-known/oauth-protected-resource. That document names the authorization server at https://www.boltopsbyelevate.com/.well-known/oauth-authorization-server. The client then runs the authorization-code flow with PKCE. Approve the scopes it asks for. No client secret is required for a public client.
A token or OAuth grant carries one or more scopes. tools/list only includes tools the credential can call. Plan filtering of that list applies only in enforce mode. Service Desk scopes follow an active or trialing Service Desk module, not the plan table below.
| Scope | Allows |
|---|---|
read | Read Bolts, intent documents, projects, comments and Bolt context. |
write | Create and update intent documents and Bolts, post comments, log activity. |
stage | Advance a Bolt through its lifecycle stages. |
branch | Set a Bolt's branch name and link it to a git connection. |
desk:read | Read Service Desk tickets, companies, SLA state and knowledge. |
desk:write | Create and update Service Desk tickets, reply, add notes and link Bolts. |
Every tool is prefixed boltops_. Anything that identifies a Bolt accepts bolt_id or bolt_code (for example BOLT-0042).
| Tool | Description |
|---|---|
boltops_whoami | Return the BoltOps organization, user and permission scopes this API token is bound to. |
boltops_list_bolts | List Bolts in the organization, newest first, with optional filters. |
boltops_get_bolt | Fetch one Bolt in full: its intent document (what we are building, user stories, acceptance criteria, edge cases, constraints, out of scope), current stage, assigned people, branch and PR, recent stage transitions, and the project it belongs to. |
boltops_get_bolt_context | Assemble everything an agent needs to actually do the work on a Bolt: the intent document, the branch name to use, the project name, and the relevant CLAUDE.md excerpt for that project. |
boltops_list_projects | List projects in the organization, including any connected git repository. |
boltops_get_intent_document | Fetch an intent document (BoltOps' lightweight PRD) by its UUID or Bolt code. |
boltops_list_comments | List comments on a Bolt, intent document, project or release, oldest first. |
| Tool | Description |
|---|---|
boltops_create_intent_document | Create a new intent document (BoltOps' lightweight PRD) and, by default, the Bolt that tracks it. |
boltops_update_intent_document | Update fields on an existing intent document. |
boltops_create_bolt | Create a Bolt for an intent document that does not have one yet. |
boltops_update_bolt | Update assignment and tracking fields on a Bolt: developer, reviewer, PR URL, and the structured bug fields on bug-type Bolts. |
boltops_add_comment | Post a comment on a Bolt, intent document, project or release. |
boltops_log_activity | Append an entry to the BoltOps activity feed. |
| Tool | Description |
|---|---|
boltops_advance_bolt_stage | Move a Bolt to a different lifecycle stage and record the transition, including how long it sat in the previous stage. |
| Tool | Description |
|---|---|
boltops_set_bolt_branch | Record the git branch (and optionally the PR URL) for a Bolt. |
| Tool | Description |
|---|---|
boltops_desk_list_tickets | List support tickets, most recently updated first. |
boltops_desk_get_ticket | Get one ticket with its full conversation (public replies and internal notes), tasks, links (Bolts, external issues) and SLA clocks. |
boltops_desk_search_knowledge | Hybrid (semantic + full-text) search over the desk's knowledge articles. |
boltops_desk_list_companies | List the customer companies on a desk (plan tag, external references, domains). |
boltops_desk_get_company | A company with its authorized contacts (roles, emergency contacts) and its open tickets. |
boltops_desk_get_sla_status | SLA clocks for a ticket: first response, next update and resolution — target, breached/met, paused, business minutes elapsed. |
| Tool | Description |
|---|---|
boltops_desk_create_ticket | Open a ticket on behalf of a customer. |
boltops_desk_reply | Send a PUBLIC reply to the customer on the ticket's channel (email, portal, Slack). |
boltops_desk_add_internal_note | Add a staff-only note to a ticket (never shown to the customer). |
boltops_desk_update_ticket | Change a ticket's state, severity, owner, category, tags or custom fields. |
boltops_desk_link_bolt | Link a ticket to an existing Bolt (the fix, enhancement or investigation). |
boltops_desk_create_article_draft | Create a DRAFT knowledge article (one symptom per article; scope line, cause, numbered steps, an Outcome line). |
boltops_desk_run_lookup | Run an allow-listed tool on one of the desk's context connectors (the customer's own system), automatically scoped to the ticket's company. |
boltops_desk_log_time | Record time spent on a ticket for level-of-effort reporting by client (e.g. |
boltops_desk_hand_off | Hand a ticket to another support team (Level 2, or back to Level 1) with a reason, posted as an internal note. |
An active 14-day trial of Growth, Pro, or Studio includes that plan's tools. Creating a token or connecting OAuth works on every plan, including Starter.
| Plan | MCP scopes |
|---|---|
| Starter | read |
| Growth | read, write, stage, branch |
| Pro | read, write, stage, branch |
| Studio | read, write, stage, branch |
| Enterprise | read, write, stage, branch |
On Starter, write, stage, and branch require the Growth plan. Compare plans on the pricing section. Service Desk tools are not part of that rule. They require an active or trialing Service Desk module.
Requests to the MCP endpoint are rate limited per organization. Studio and Enterprise have higher limits than other plans. A limited request receives HTTP 429 with a Retry-After header.
Join engineering teams that have replaced sprint ceremonies with AI-orchestrated workflows.