Tradify MCP
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 and used to authenticate with the hosted Cotlet.dev server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tradify through Cotlet.dev. Call tradify_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 |
|---|---|
| tradify_guideA | How to work in Tradify (create jobs, quotes and invoices and book staff): its screens and the sign-in link. Call this first. |
| tradify_statusA | Check that your Cotlet.dev account and Tradify are ready: account, credits and Tradify connection. |
| tradify_openB | Open a Tradify page in your signed-in Cloud Browser (default https://go.tradifyhq.com) to work with create jobs, quotes and invoices and book staff. |
| tradify_readB | Read the current Tradify page: its text and numbered buttons, links and fields. |
| tradify_clickB | Click a numbered element on the current Tradify page. |
| tradify_typeB | Type text into a numbered field on the current Tradify page. |
| tradify_closeA | Close the Tradify 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 browser loop (open, read, click, type, close) is crisply separated by verb, and guide vs. status target different concerns. Minor overlap remains between tradify_guide and tradify_status, both of which act as onboarding gates ('call this first' vs. readiness check), which could cause an agent to pick the wrong starting tool.
All seven tools use a consistent snake_case tradify_ prefix, making the set easy to scan. However, five are action verbs (open, read, click, type, close) while guide and status are nouns, a small deviation from a pure verb_noun convention.
Seven tools is a tight, well-scoped surface for a browser-driven automation server. Every tool earns its place: one for guidance, one for precondition checks, four for the interact loop, and one for teardown/credit control.
The open/read/click/type/close loop covers the essential lifecycle for driving the Tradify web UI, with a guide and status check for onboarding. Gaps exist for handling dynamic pages (no wait, scroll, select/dropdown, or keyboard-submit operation), which agents may hit on richer flows like line-item entry on quotes and invoices.