Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Joist MCP Invoice Sarah Lee $2,300 for Tuesday's tile job, due in 14 days."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Yes, ChatGPT, Claude and other AI agents can work in your Joist account. Joist has no public API and no official MCP server. Cotlet.dev connects your own signed-in Joist account to any AI agent, so you can ask in plain words and the AI writes estimates, sends invoices and keeps your client list up to date for you.
Write an estimate for Mike Torres: replace 40 ft of deck boards, $1,850 labor plus $640 materials.
Which invoices have been unpaid for more than 30 days? List client, amount and due date.
Invoice Sarah Lee for Tuesday's bathroom tile job, $2,300, due in 14 days.
Add a new client, Dave Patel, 555-0142, 18 Oak Street, and draft an estimate for a kitchen faucet swap.
Send a friendly payment reminder to every client with an invoice overdue since last Friday. Show me the drafts first.
Related MCP server: Taskade MCP Server
Get your API key at https://cotlet.dev/app and export it as COTLET_API_KEY.
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"Settings → Apps → add connector URL https://cotlet.dev/mcp/v1, then sign in with Cotlet.dev. No API key needed.
Copy .cursor/mcp.json from this repo into your project:
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}This repo is a real MCP server. It speaks MCP over stdio, lists its Joist tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.
{"mcpServers":{"joist":{"command":"uvx","args":["joist-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}Or with Docker:
docker build -t joist-mcp .
docker run -i --rm -e COTLET_API_KEY joist-mcpTools: joist_guide, joist_status, joist_open, joist_read, joist_click, joist_type, joist_close. Without COTLET_API_KEY a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".
Python 3.10+, nothing else to install. From PyPI:
pip install joist-mcp # or run it once: uvx joist-mcp connect
joist-mcp connectOr straight from this repo:
export COTLET_API_KEY="your-key"
python3 joist_agent.py connect # ready config for Claude Code, Cursor, ChatGPT
python3 joist_agent.py status # is Joist ready in your Cotlet.dev account
python3 joist_agent.py guide # Joist screens and sign-in link
python3 joist_agent.py read # open Joist, read the page, close the browser
python3 joist_agent.py tools # list Cotlet.dev tools
python3 joist_agent.py serve # start the stdio MCP server (same as no argument)Does Joist have an API for developers?
Joist has no public, documented API for developers. Cotlet.dev works in your own Joist account directly, so your AI agent can create estimates, send invoices and look up clients without one.
How do I connect Joist to ChatGPT?
There is no official Joist app in ChatGPT. Add Cotlet.dev as an app in ChatGPT (Settings → Apps, connector URL https://cotlet.dev/mcp/v1), sign in to Joist once in your Cotlet.dev Cloud Browser, and ask ChatGPT in plain words. No code and no Joist API key.
Is there a way to use Claude with Joist?
Yes. In Claude Code run the one-line claude mcp add command above; in the Claude app add https://cotlet.dev/mcp/v1 as a custom connector. Claude then works in your own Joist account.
Is there a Joist MCP server?
Joist has no official MCP server. Cotlet.dev is a hosted MCP server that works in your Joist account for you, with ChatGPT, Claude, Cursor, Codex and n8n.
Start free: https://cotlet.dev/signup?app=joist&utm_source=github&utm_medium=readme&utm_campaign=joist
Click a numbered element on the current Joist page.
Inputs: element (required).
Close the Joist browser session when the work is done, so credits stop running.
Inputs: no named parameters.
How to work in Joist (estimates, invoices and clients): its screens and the sign-in link. Call this first.
Inputs: task.
Open a Joist page in your signed-in Cloud Browser (default https://pro.joistapp.com) to work with estimates, invoices and clients.
Inputs: url.
Read the current Joist page: its text and numbered buttons, links and fields.
Inputs: element.
Check that your Cotlet.dev account and Joist are ready: account, credits and Joist connection.
Inputs: no named parameters.
Type text into a numbered field on the current Joist page.
Inputs: text (required), element (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool maps to a distinct step in a browser workflow (guide, status, open, read, click, type, close), so misselection risk is low. The only mild overlap is between joist_guide (instructions/screens) and joist_status (account and connection readiness), both described as first-call tools, which could cause a hesitant agent to pick the wrong one initially.
All tools use the same joist_ prefix followed by a short, lowercase verb (guide, status, open, read, click, type, close). The pattern is predictable and readable throughout.
Seven tools is a tight, well-scoped set for a browser-automation wrapper: one per primitive action plus onboarding/status helpers. No tool feels redundant or out of place.
The surface covers the core loop (open, read, click, type, close) plus onboarding, but generic browser primitives like selecting a dropdown option, pressing keys/Enter, scrolling, or waiting for page loads are absent. In Joist forms with dropdowns or multi-step flows, these gaps could create dead ends, though agents may work around some by clicking.
Joist MCP server for ChatGPT, Claude and any AI agent: create estimate, convert estimate to invoice, list invoices, add client and record payment in your own Joist account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Joist yourself; Cotlet does not store your password and you need no Joist API key. About the official Joist API: Joist has no public API (checked 26 Oct 2026): its help center and pricing page document none, and there are no webhooks. The only built-in link out is QuickBooks Sync, part of Joist Pro, which copies issued estimates and invoices to QuickBooks Online once a night. Setup and FAQ: https://cotlet.dev/integrations/joist-api-mcp-server
Contractor+ MCP server for ChatGPT, Claude and any AI agent: create estimate, send estimate, create job, send invoice and list unpaid invoices in your own Contractor+ account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Contractor+ yourself; Cotlet does not store your password and you need no Contractor+ API key. About the official Contractor+ API: Contractor+ has a public API with an account API key, but it comes with the Pro Team plan, together with Zapier; Freedom and Pro do not include it (checked 8 Nov 2026). There is no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/contractor-plus-api-mcp-server
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Jobber MCP server for ChatGPT, Claude and any AI agent: create quote, convert quote to job, create invoice, send invoice and list unpaid invoices in your own Jobber account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Jobber yourself; Cotlet does not store your password and you need no Jobber API key. About the official Jobber API: Yes, Jobber has a GraphQL API in its Developer Center (checked 14 Oct 2026), but you cannot use it without registering an app. Each Jobber account authorizes your app with OAuth 2.0 and tokens must be refreshed. Setup and FAQ: https://cotlet.dev/integrations/jobber-api-mcp-server
