ServiceBox 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 for Authorization Bearer authentication. 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.
ServiceBox through Cotlet.dev. Call servicebox_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 |
|---|---|
| servicebox_guideA | How to work in ServiceBox (dispatch work orders, compare job costs and manage quotes and invoices): its screens and the sign-in link. Call this first. |
| servicebox_statusA | Check that your Cotlet.dev account and ServiceBox are ready: account, credits and ServiceBox connection. |
| servicebox_openB | Open a ServiceBox page in your signed-in Cloud Browser (default https://jb.jobboxsoft.com) to work with dispatch work orders, compare job costs and manage quotes and invoices. |
| servicebox_readA | Read the current ServiceBox page: its text and numbered buttons, links and fields. |
| servicebox_clickB | Click a numbered element on the current ServiceBox page. |
| servicebox_typeB | Type text into a numbered field on the current ServiceBox page. |
| servicebox_closeA | Close the ServiceBox 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 of browser work: guide/status for setup checks, open/close for session lifecycle, and read/click/type for page interaction. The guide and status tools have slightly different purposes (instructions vs readiness diagnostics), and no two tools appear interchangeable.
All tools share a clear servicebox_ prefix and are readable, with mostly action-oriented names (open, read, click, type, close). The nouns guide and status are minor deviations from the verb pattern but remain predictable.
Seven tools is well-scoped for a browser-automation workflow: a compact setup, interaction, and cleanup loop without redundant tools.
The core browser lifecycle is covered: open a page, read it, click and type on numbered elements, then close the session. Minor gaps exist around navigation/history, waits, or richer form controls, but agents can work around them via links and repeated reads.