Extrabat 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, used to authenticate and execute tools against your connected Extrabat account. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Extrabat through Cotlet.dev. Call extrabat_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 |
|---|---|
| extrabat_guideA | How to work in Extrabat (customers, quotes, site visits and after-sales): its screens and the sign-in link. Call this first. |
| extrabat_statusA | Check that your Cotlet.dev account and Extrabat are ready: account, credits and Extrabat connection. |
| extrabat_openB | Open a Extrabat page in your signed-in Cloud Browser (default https://myextrabat.com) to work with customers, quotes, site visits and after-sales. |
| extrabat_readA | Read the current Extrabat page: its text and numbered buttons, links and fields. |
| extrabat_clickB | Click a numbered element on the current Extrabat page. |
| extrabat_typeC | Type text into a numbered field on the current Extrabat page. |
| extrabat_closeA | Close the Extrabat 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 distinct phase or primitive of a browser-automation workflow: status (account/credit check), guide (instructions), open (navigation), read (page inspection), click, type, and close. There is no meaningful overlap between read/click/type/close since they operate on different page interactions, and status vs guide is clearly separated by 'check readiness' vs 'how to work'.
All seven tools use the same snake_case 'extrabat_<verb>' convention with a shared namespace prefix. No camelCase mixing or vague standalone verbs; the pattern is immediately predictable.
Seven tools is exactly the right scope for a minimal browser-automation agent: one setup check, one guide, and the five core primitives needed to open, read, interact with, and close a session. Every tool earns its place with no filler.
The surface covers the full session lifecycle (status → guide → open → read → click/type → close), which matches the stated purpose. Minor gaps remain for richer page interaction—no dedicated select/option handling, scrolling, or explicit navigation/back beyond 'open'—but agents can work around these via click and re-open.