Crimp Professional · MCP
Let your AI look up real components, calculate a wire or DC-DC charger circuit, and build a small electrical plan. Crimp does the calculations. You inspect the assumptions and edit the drawing.
Requires an active Crimp Professional plan and a connection key. View Professional pricing.
1 · Connect
In Crimp, open your account menu → Professional workspace → Connect AI tools (MCP). Create a key and copy it once. You can replace or revoke it there any time.
Save the key as CRIMP_MCP_KEY in your client’s private environment. Keep it out of chats, shared configuration files and URLs.
Add this to ~/.codex/config.toml, keeping your other settings. Update an existing Crimp entry if you have one:
[mcp_servers.crimp]
url = "https://crimp.studio/api/mcp"
bearer_token_env_var = "CRIMP_MCP_KEY"Start Codex with the environment variable available, then use /mcp to check the connection.
Add this server to your MCP configuration, with CRIMP_MCP_KEY in your private environment:
{
"mcpServers": {
"crimp": {
"type": "http",
"url": "https://crimp.studio/api/mcp",
"headers": { "Authorization": "Bearer ${CRIMP_MCP_KEY}" }
}
}
}Restart Claude Code and use /mcp to check the connection.
Use Streamable HTTP at https://crimp.studio/api/mcp with an Authorization: Bearer <your key> header. Your client must support custom bearer credentials.
ChatGPT’s custom connections require OAuth and cannot use this key-based connection. The earlier no-authentication setup no longer works.
The Crimp skill explains tool usage; it does not connect or authenticate the tools.
2 · Ask
Start a new chat and paste this request:
Use Crimp to look up the Victron Orion XS 50 A DC-DC charger. Show its catalog ID, listed input voltage and output current.
Look for a Crimp tool call and a catalog ID in the response. A general answer without a Crimp tool call does not confirm the connection. If no tool runs, check that Crimp is enabled in your client and start a new chat.
Then try a planning task. Your AI should ask for missing installation facts and report assumptions alongside the result.
Calculate a circuit
“Use Crimp to size the wire for my 12 V fridge circuit. Ask for the load and installation details first, then compare 3 m and 5 m one-way runs.”
Build a draft
“Use Crimp to plan a DC-DC charger circuit for my boat. Ask for the batteries, charger, charging limits and cable lengths. Give me a draft link with its assumptions.”
Check a system
“Use Crimp to analyze this exported Crimp project. Explain the highest-priority findings and what installation evidence is still missing.”
Provide the exported project file to your agent. Crimp’s tools cannot read your account’s saved projects.
3 · Review
A draft result includes a direct Crimp review link. Open it to see a view-only schematic, assumptions and current checks. Choose Edit a copy when you want a separate editable local project.
Drafts support up to 10 counted equipment components. The tools apply Crimp’s supported ABYC E-11 calculations and checks; a result is planning assistance, not installation approval or compliance certification.
For developers
The calling agent supplies facts and topology; Crimp computes the results. Calls do not access saved projects or run a language model. API version 1.
GET /api/agent-tools returns the current tool descriptions and JSON input schemas. Use discovery as the authority for accepted fields.
curl https://crimp.studio/api/agent-tools \
-H "Authorization: Bearer $CRIMP_MCP_KEY"
curl https://crimp.studio/api/agent-tools \
-H "Authorization: Bearer $CRIMP_MCP_KEY" \
-H 'Content-Type: application/json' \
-d '{"tool":"search_components","arguments":{"query":"Orion"}}'Both discovery and calls require the same Professional connection key. A missing or revoked key returns 401; expired Professional access returns 403. Create or revoke keys in your Professional workspace.
Each POST accepts one {tool, arguments} object. Successful calls return {ok:true, tool, metadata, data}; tool errors return {ok:false, tool, metadata, error}. Metadata identifies the API, engine and project schema versions. HTTP-level rejection may return a transport error instead.
| Tool | Use it for |
|---|---|
search_components | Find catalog IDs for a part or category. |
get_component | Retrieve a component’s specifications, terminals, declared configuration and catalog provenance. |
calculate_circuit | Size a wire or DC-DC charger using the calculator’s explicit installation inputs. |
analyze_system | Review a supplied Crimp system graph and inspect circuit findings. |
create_draft | Build a catalog-based topology, analyze it and return a link to review it in Crimp. |
create_draft accepts {draft:{name, components, connections, assumptions}}. Component entries use real catalog IDs and explicit estimated flags. Connections identify component refs, ports, polarity and one-way cable length in metres. The discovery schema describes every required field.
The returned reviewUrl carries a bounded draft in its URL fragment. Opening it immediately shows a view-only schematic without signing in or creating a project. Agents should present the exact URL as a clickable HTTPS link, not a local HTML preview. Choose Edit a copy to create a new local project. Your existing project is saved before switching. No cloud project or public share is created by the API.
The link contains the draft: treat it as information you are sharing with its recipient. Crimp removes the fragment before starting browser analytics and keeps a bounded copy in this tab’s session storage so a reload can recover the review. Importing or dismissing clears that copy. The draft is recalculated when opened; an incompatible engine-version link must be recreated.
The authenticated endpoints emit bounded operational records containing the tool name, MCP or HTTP transport, success or error category, and duration. These records do not contain tool arguments, results or caller identifiers. Draft review links include a coarse transport label, and the app’s existing analytics records review opens and imports without the draft content. The label is not a user or request identifier.
Requests and graphs are bounded; HTTP request bodies are limited to 256 KiB and draft handoff payloads to 64 KiB. Best-effort rate limits protect the endpoints; these are not a strict global quota or a service-level guarantee. Respect 429 and Retry-After, and retry transient failures with backoff. Correct invalid input before retrying.
Send only the project data needed for the requested calculation. Existing project and sharing credentials are neither required nor supported by this API.
Email [email protected] with your AI client, the setup step and any error message. For tool failures, include the tool name and a small example without private project data.