AI & Agents
Connect AI Tools to Tidyflow with MCP
Connect Claude Code, Codex, Cursor, and other MCP-compatible AI tools to your live Tidyflow workspace.
Tidyflow exposes a Model Context Protocol (MCP) endpoint. Any MCP-compatible tool can connect to your live workspace and work with your data. That includes coding agents like Claude Code, Codex, and Cursor, plus other clients that support remote MCP servers.
Connections act with your own account’s permissions: a connected tool can only see and do what you can.
Before you start
- Workspace AI must be enabled. An owner or admin accepts the AI terms of use once for the workspace.
- You must give your personal consent. Each user opts in for their own data, and connected tools stop working without it.
- You need an MCP-compatible tool that supports remote (streamable HTTP) MCP servers with OAuth.
Step 1: Enable AI in Tidyflow
- Go to Settings → Artificial intelligence.
- If you’re an owner or admin and AI is not enabled yet, tick I have read and accept the AI terms of use, choose the delegated client access, and click Enable AI. This also records your personal consent.
- If AI is already enabled for the workspace, go to Personal consent and click Grant consent.
See Turn on AI for your firm for the full enablement steps.
Step 2: Copy your MCP URL
- Still in Settings → Artificial intelligence, go to Connections.
- Next to MCP URL, click Copy URL.
The URL looks like https://app.tidyflow.com/mcp.
If you don’t see the MCP URL
The Connections section shows the MCP URL only once AI is enabled for the workspace. Until then, the MCP access row explains why:
- “Enable workspace AI above first” means you are an owner or admin and the workspace AI terms have not been accepted. Enable AI on the same page.
- “Ask an owner or admin to enable AI for your workspace” means your firm hasn’t accepted the AI terms of use yet. An owner or admin accepts them on the same page.
- “Not available for this workspace” means MCP access is turned off for your workspace. Contact Tidyflow support if you see this.
The URL can show before you have given your personal consent, but a tool cannot connect until you do. Grant it under Personal consent at the top of the page.
Step 3: Add the endpoint to your AI tool
Add the MCP URL to your tool as a remote (streamable HTTP) MCP server. The exact steps vary by tool, so check its MCP documentation.
Claude Code
claude mcp add --transport http tidyflow https://app.tidyflow.com/mcp
Codex
Add the server to ~/.codex/config.toml:
[mcp_servers.tidyflow]
url = "https://app.tidyflow.com/mcp"
Then sign in to authorize it:
codex mcp login tidyflow
Cursor and other tools
Add a new remote (streamable HTTP) MCP server and paste the same URL. No API key or manual token is needed; you authorize in the next step.
Step 4: Authorize the connection
The first time your tool connects, for example when you run codex mcp login or first use the server in Claude Code, it opens your browser to sign in to Tidyflow and approve access. Once you approve, the tool is connected and works with your live workspace.
What connected tools can do
- Query your clients, contacts, jobs, invoices, payments, proposals, and services
- Create clients and jobs, including unassigned or tagged jobs
- Update job names, dates, statuses, assignees, tags, billing fields, and descriptions
- Read and add job comments
- Manage job tags
- Draft proposals and preview totals
- Create and update email drafts in your inbox for you to review and send. Connected tools can never send email
Every action runs with your own permissions, and the tool confirms only the actions it actually completed.
Manage or disconnect a tool
- Go to Settings → Artificial intelligence.
- Under Connections, each connected tool is listed with when it was last used and when it connected.
- Click Revoke next to a tool to disconnect it.
To disconnect every tool for your user at once, click Revoke consent under Personal consent at the top of the same page.
Related articles
Was this page helpful?
What went wrong?
Thanks for your feedback.
- Previous
- Zapier integration
Last updated October 12, 2026