Torque360 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Used as the Authorization Bearer token for the hosted MCP server or passed to the local stdio server. Without it, tool calls fail with an instruction to set COTLET_API_KEY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Torque360 through Cotlet.dev. Call torque360_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 |
|---|---|
| torque360_guideA | How to work in Torque360 (shop reports, technician hours, inspection templates and pricing): its screens and the sign-in link. Call this first. |
| torque360_statusA | Check that your Cotlet.dev account and Torque360 are ready: account, credits and Torque360 connection. |
| torque360_openA | Open a Torque360 page in your signed-in Cloud Browser (default https://portal.torque360.co) to work with shop reports, technician hours, inspection templates and pricing. |
| torque360_readB | Read the current Torque360 page: its text and numbered buttons, links and fields. |
| torque360_clickB | Click a numbered element on the current Torque360 page. |
| torque360_typeB | Type text into a numbered field on the current Torque360 page. |
| torque360_closeA | Close the Torque360 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
The core interaction tools (read, click, type) target clearly different actions on numbered page elements, and open/close bracket the session lifecycle distinctly. The only mild overlap is between guide (instructions) and status (account/connection readiness), which an agent could occasionally conflate when troubleshooting.
Every tool follows the same predictable torque360_<verb> pattern (read, click, type, close, guide, status, open), with no camelCase mixing or alternate verb styles. The shared prefix also makes the server's scope immediately obvious.
Seven tools is well-scoped for a browser-automation wrapper: each tool maps to one necessary capability (orient, open, read, click, type, check, close). Nothing feels redundant or missing at the count level.
The surface covers the full session lifecycle: status check, guide, open, read, click, type, and close, so core workflows on shop reports and pricing are achievable. Minor gaps exist for navigation (back/scroll), waiting for page loads, or verifying post-action state, but agents can work around these with repeated read calls.