Accelo 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. Required to use the Accelo MCP server (Claude Code, Cursor, local stdio, or Docker). Without it, tool calls answer: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Accelo through Cotlet.dev. Call accelo_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 |
|---|---|
| accelo_guideA | How to work in Accelo (manage tickets, projects, time and quotes): its screens and the sign-in link. Call this first. |
| accelo_statusA | Check that your Cotlet.dev account and Accelo are ready: account, credits and Accelo connection. |
| accelo_openB | Open a Accelo page in your signed-in Cloud Browser (default https://accelo.com) to work with manage tickets, projects, time and quotes. |
| accelo_readB | Read the current Accelo page: its text and numbered buttons, links and fields. |
| accelo_clickB | Click a numbered element on the current Accelo page. |
| accelo_typeB | Type text into a numbered field on the current Accelo page. |
| accelo_closeA | Close the Accelo 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 maps to a single, clearly distinct browser-automation primitive (guide, status, open, read, click, type, close) with no overlapping responsibilities. The read/click/type triad is a standard, well-understood workflow where boundaries are unambiguous.
All seven tools use the same accelo_ prefix with a short, consistent verb (guide, status, open, read, click, type, close). No mixing of camelCase, casing, or verb styles.
Seven tools is a tight, well-scoped set for driving a web app through a cloud browser; each tool earns its place and nothing looks redundant. It sits comfortably in the 3-15 ideal range.
The core loop (open, read, click, type, close) plus onboarding and status is present, but common browser actions like scrolling, waiting for page load, pressing Enter/keys, or selecting dropdowns are absent. These gaps will likely force agents into failed attempts on forms and long pages.