Ontraccr MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotraccr API key from 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.
Ontraccr through Cotlet.dev. Call ontraccr_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 |
|---|---|
| ontraccr_guideB | How to work in Ontraccr (crew time cards, form approvals, field shifts, project budgets and board cards): its screens and the sign-in link. Call this first. |
| ontraccr_statusB | Check that your Cotlet.dev account and Ontraccr are ready: account, credits and Ontraccr connection. |
| ontraccr_openB | Open a Ontraccr page in your signed-in Cloud Browser (default https://app.ontraccr.com/login) to work with crew time cards, form approvals, field shifts, project budgets and board cards. |
| ontraccr_readA | Read the current Ontraccr page: its text and numbered buttons, links and fields. |
| ontraccr_clickB | Click a numbered element on the current Ontraccr page. |
| ontraccr_typeB | Type text into a numbered field on the current Ontraccr page. |
| ontraccr_closeA | Close the Ontraccr 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 set splits cleanly into meta tools (guide, status), browser lifecycle (open, close), and page interaction (read, click, type), each with a distinct role. The only mild overlap is guide vs. status, both being 'call before doing work' orientation tools, but their descriptions clearly separate onboarding instructions from connectivity/credit checks.
Every tool uses the same ontraccr_<verb> snake_case pattern with a short, single-purpose verb. There are no mixed conventions or variant spellings, so the pattern is fully predictable.
Seven tools is tightly scoped for a browser-automation wrapper: two setup/readiness tools, three interaction primitives, and open/close lifecycle. Nothing appears redundant and no obvious primitive is missing from the count.
The core agent loop (open a page, read it, click/type, close) is fully covered, plus guidance and status checks. Minor gaps remain for common DOM interactions such as scrolling, selecting dropdown options, or pressing keys, which agents will have to work around via clicking and typing.