Tradify by Cotlet MCP server

Tradify API and MCP server, self-hosted

A Tradify API and a Tradify MCP server you run on your own computer, in Python, on the session of your own Google Chrome. All 15 Tradify tools we run in production at Cotlet: jobs and job status, customers, quotes with line items, invoices from quotes, quote and invoice email, payments, and the Scheduler.

Tradify has no public API, no API keys, no webhooks and no official MCP server. Its accounting connectors (Xero, QuickBooks, Sage) sync invoices and bills, not jobs, quotes or the schedule. This repo gives you:

• MCP server for Claude Code, Claude Desktop, Cursor, Codex and any MCP client, over stdio or HTTP. Setup
• REST API on http://127.0.0.1:8787/api/v1/tradify, with OpenAPI docs at /docs. Setup
• Python: call("list_invoices", {"status": "overdue"}), plus 9 ready scripts in examples/.

It is for technical people who want to run it themselves, for noncommercial use only (license). If you want it running 24/7 on a server, kept working when Tradify changes its web app, for a team or a business, use the hosted version at cotlet.dev.

git clone https://github.com/cotletdev/tradify-api-mcp-server.git && cd tradify-api-mcp-server
python3 -m venv .venv && . .venv/bin/activate && pip install -e .
tradify-mcp connect                                # reads your Tradify session from Chrome
tradify-mcp call list_jobs
claude mcp add tradify -- "$PWD/.venv/bin/tradify-mcp" mcp

Contents

• How it works
• Requirements
• Install
• Connect your Chrome
• MCP server
• REST API
• Python and the example scripts
• All 15 tools
• Configuration
• Security and your Tradify account
• Errors
• Self-hosted or hosted

How it works

AI agent (MCP) / script (REST, Python) ──▶ tradify-mcp on your computer ──your cookies──▶ go.tradifyhq.com
                                                  ▲
                        tradify-mcp connect ──────┘ reads them once from your Chrome (DevTools Protocol)

1. You sign in to Tradify in your own Chrome at go.tradifyhq.com, the way you always do: username, Continue, password. Tick Keep me logged in.
2. tradify-mcp connect attaches to that Chrome through the Chrome DevTools Protocol, reads the tradifyhq.com cookies and saves them to ~/.config/tradify-api-mcp/session.json, readable by your user only. It never sees or stores your password or a 2-Step code.
3. Every tool call is a request to the /api the Tradify web app itself calls, with those cookies, sent with curl_cffi, which copies Chrome's TLS fingerprint. Calls that change something carry the app's antiforgery token, read fresh for each tool run. No headless browser runs.

The session lives in one cookie, SessionId. With Keep me logged in Tradify keeps it for about a month. When Tradify signs you out, the server reads the cookies from Chrome again, if Chrome is open with remote debugging on.

Requirements

Shortened. The full README is on GitHub.