BoltWright MCP
Your agent.
Your shop’s records.
Bring the agent you work with into your commercial HVAC shop. Look up the schedule, follow a unit’s history and help the office move the work along.
Useful across
the whole shop.
MCP gives an outside agent the same business tools Bolt uses, filtered to the person who signs in. An office account and a technician account see the work their roles allow.
“What’s on my schedule tomorrow?”
“Show me the open findings on this unit.”
“Draft a quote for the repair.”
Example requests. Available tools depend on your role and the access you grant.
Connect from your agent app.
You need a BoltWright account. For Claude, open BoltWright in Claude’s connector directory and connect with read-only access. For other apps that support remote MCP servers, OAuth and automatic client registration, follow the steps below.
Add a remote MCP server.
Name it BoltWright and paste
https://app.boltwright.com/mcpinto the server URL field. Choose OAuth if the app asks for an authentication method.Sign in and choose access.
Use your usual BoltWright sign-in. Check the app name and return address. Start with Read only, or choose Read and write when you want the app to request changes.
Ask about the work.
Start with your schedule or an equipment-history question. The app discovers the tools your account can use. No separate API key or Field token is needed.
Your permissions.
Your decisions.
Only connect an app you trust with your shop’s records. The app handles information it receives under its own policies.
How connected apps handle informationRead only
Look up permitted customers, sites, equipment, jobs, schedules, reports, quotes, invoices, stock, notes and hours. It cannot change records or approve a proposal.
Read and write
The app can request ordinary internal changes. Customer messages and other consequential actions prepare a saved proposal. The app must show it to you and get your later acceptance before confirming it.
Disconnect when you need to.
Open Connected agent apps under Account & appearance in Office. Disconnecting stops future access; an operation already dispatched may finish. Copies the app already received remain with it.
For people building agents.
The hosted interface reuses BoltWright’s business permissions, operation receipts and approval journal. There is one set of rules across Office, Field, Bolt and MCP.
- Server URL
https://app.boltwright.com/mcp- Transport
- Stateless Streamable HTTP with JSON responses. No SSE stream or transport session.
- Protocol versions
2025-11-25,2025-06-18,2025-03-26- Account linking
- Authorization code with S256 PKCE and dynamic client registration. Public OAuth clients; no client secret.
- Scopes
boltwright:read, with optionalboltwright:write. Consent may narrow a write request to read only.- Discovery
- Protected resource metadata and authorization server metadata
- Token lifetime
- Access tokens last up to 15 minutes. Refresh tokens rotate; connections expire after 30 days. Reconnect if a refresh response is lost.
- Calls and retries
- Pass a stable
_bolt.operation_idfor each exact operation. Continue with the returned_bolt.conversation_id. Retry an uncertain result with the same identity. - Confirmations
- Show the saved proposal and obtain the person’s later acceptance before calling
confirm_actionin that conversation. The server binds the proposal and execution; the host is responsible for obtaining the human decision. - Agent reference
- Plain-text connection and tool guide
Need a hand connecting your app? Email us. Looking at BoltWright for your shop? Book a walkthrough.