AutoRepair Cloud MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | No | API key from your Cotlet.dev console, used for editor/script connections and the local Python bridge (sent as the Bearer token in the Authorization header). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
AutoRepair Cloud through Cotlet.dev. Call autorepair_cloud_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| autorepair_cloud_guideA | How to work in AutoRepair Cloud (repair quotes, workshop bookings, parts and shop reports): its screens and the sign-in link. Call this first. |
| autorepair_cloud_statusA | Check that your Cotlet.dev account and AutoRepair Cloud are ready: account, credits and AutoRepair Cloud connection. |
| autorepair_cloud_openB | Open a AutoRepair Cloud page in your signed-in Cloud Browser (default https://autorepaircloud.com/login) to work with repair quotes, workshop bookings, parts and shop reports. |
| autorepair_cloud_readA | Read the current AutoRepair Cloud page: its text and numbered buttons, links and fields. |
| autorepair_cloud_clickC | Click a numbered element on the current AutoRepair Cloud page. |
| autorepair_cloud_typeC | Type text into a numbered field on the current AutoRepair Cloud page. |
| autorepair_cloud_closeA | Close the AutoRepair Cloud browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: guide, status, open, read, click, type, and close map to separate phases or browser actions. There is no meaningful overlap between reading, clicking, typing, opening, and closing.
All tools consistently use the autorepair_cloud_ prefix followed by a short action-oriented name. The snake_case pattern is predictable throughout.
Seven tools is well-scoped for a browser-based workflow server. Each tool covers an essential step: orientation, readiness, session lifecycle, and page interaction.
The surface covers the core browser workflow: open, read, click, type, close, plus guidance and status checks. Minor gaps exist around explicit navigation, waiting, scrolling, and select/dropdown handling, but most tasks can likely be worked around with read/click/type.