AI · Claude

The Claude checklist integration that works in your name.

Connect Claude to CheckFlow and ask in plain language: what is overdue, start the onboarding for Sam, turn this procedure into a template. Claude does the clicking, with your permissions, and every change is recorded against you.

Start free trialConnecting a client (docs)

MCP server on every planUses no AI creditsActs only as you

Claude Codehttps://api.checkflow.io/mcp

Add the server

claude mcp add --transport http checkflow https://api.checkflow.io/mcp

Sign in, inside Claude Code

/mcp
# choose checkflow, then Authenticate.
# Sign in to CheckFlow in your browser and click Allow.
Add --scope user to use it in every project. EU workspaces use api-eu.checkflow.io.
In short

Last updated

Claude connects to CheckFlow through the CheckFlow MCP server. Add it as a custom connector in Claude on the web, desktop or mobile, or to Claude Code, and sign in with your CheckFlow account: Claude then works as you. It can read your Tasks Grid, start checklists, fill in fields, complete tasks and build templates. An API key still works where you would rather not sign in.

Ask Claude, and the work happens in CheckFlow.

No switching tabs

Check what is due, start a checklist or note an answer from the conversation you are already having with Claude.

Procedures become templates

Paste a written procedure and Claude builds a CheckFlow template from it, checked against CheckFlow’s own rules before it is saved.

Still accountable

Claude sees only what you can see, is refused wherever you would be, and its changes are recorded in your name.

Today

Which Claude apps can connect

The CheckFlow MCP server takes two ways in. You can sign in with your CheckFlow account (OAuth), and Claude then works as you, with no key to store. Or you can send an API key in an X-API-KEY header, for an assistant that should act as someone else or as the workspace.

How each Claude app connects to the CheckFlow MCP server, as at October 2026
Claude appConnects?How
Claude on the webYes, by signing inSettings, then Connectors, then Add custom connector with the server address; then Connect
Claude DesktopYesThe Connectors screen signs in, as on the web. With an API key, the mcp-remote bridge in the developer config (needs Node.js 18 or later)
Claude mobile appsYes, by signing inA connector added on the web is also available on mobile
Claude CodeYesclaude mcp add, then /mcp and Authenticate to sign in, or the --header option for a key
Claude API (MCP connector)Yes, with a keySend the API key as the authorization token; it arrives as Authorization: Bearer

CheckFlow is not in Claude’s connector directory, so you add it as a custom connector. On a Team or Enterprise plan, an Owner may need to add the connector for your organisation first. Each person then connects and signs in as themselves, so changes stay in their own name.

Web, desktop and mobile

Add CheckFlow as a custom connector

  1. 01

    Add the connector

    In Claude, open Settings, then Connectors, and choose Add custom connector. Name it CheckFlow and enter https://api.checkflow.io/mcp, or https://api-eu.checkflow.io/mcp if your workspace is in the EU.

  2. 02

    Connect and sign in

    Click Connect. CheckFlow opens in your browser: sign in the way you normally do, with your password, Google, Microsoft or your company’s single sign-on.

  3. 03

    Check, then allow

    CheckFlow shows what Claude will be able to do, which workspace it is for and where it will send you back. Check them, then click Allow.

  4. 04

    Ask a first question

    Ask “Which CheckFlow workspace are you connected to?” and Claude answers from get_workspace_info. The connector is also there in Claude Desktop and the mobile apps.

Administrators, and Members with the AI.Assistant permission, can connect Claude; new Members have it. Guests can’t. If you belong to more than one workspace, switch to the right one in CheckFlow before you connect.

Claude Desktop

Claude Desktop with an API key

Claude Desktop’s Connectors screen signs in, as above. To connect with an API key instead, ask an Administrator for a key created on the API & Integrations tab of Team Management, acting as the member Claude should work as. In Claude Desktop, open Settings, then Developer, and click Edit Config. Add a checkflow entry under mcpServers that runs the mcp-remote bridge, as shown, with your key in the env block.

Save the file and restart Claude Desktop. The CheckFlow tools appear in the tools menu of a new conversation. Ask “Which CheckFlow workspace are you connected to?” and Claude answers from get_workspace_info.

  • Write the header with no space after the colon, as shown
  • Keep the key in env, not in a file you sync or share
  • Use the api-eu address if your workspace is in the EU
Connecting a client (docs)
Claude Desktopclaude_desktop_config.json

mcpServers

{
  "mcpServers": {
    "checkflow": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://api.checkflow.io/mcp",
        "--header", "X-API-KEY:${CHECKFLOW_API_KEY}"
      ],
      "env": { "CHECKFLOW_API_KEY": "your-api-key-here" }
    }
  }
}
Some platforms split arguments on spaces, which would break the header.

What it can do

What Claude can do in CheckFlow

The MCP server has 147 tools in eight families. These are a few, with the real tool names Claude calls.

  • Your work

    “What’s on my plate this week?” Claude reads your Tasks Grid with list_my_work, filtered to what is due.

  • Start checklists

    “Start an Invoice Review for INV-2041, due Friday.” create_checklist runs the template with its parameters filled in.

  • Complete tasks

    “Mark the bank details check done and note the IBAN was verified by phone.” set_task_fields, add_task_comment and complete_task.

  • Find what’s stuck

    “Which supplier onboardings have stalled?” search_checklists and get_checklist_activity show where each one stopped.

  • Keep lists current

    “Add these twelve suppliers to the Suppliers Data Set.” create_data_set_records adds them in one call.

  • Set up schedules

    “Start the weekly stock check every Monday at 9am.” create_schedule creates the recurring run.

Every tool tells Claude whether it only reads, changes something or deletes something, so Claude can ask you before a destructive step. The full list is in the MCP server docs.

Templates

How Claude turns a procedure into a template

  1. 01

    It reads your workspace

    get_workspace_info returns your members, groups, tags and templates, so steps are assigned to people and groups that exist.

  2. 02

    It reads the rules

    get_authoring_guide explains how CheckFlow templates are built: tasks, the 19 field types, conditions, due dates, halts and notifications.

  3. 03

    It drafts and checks

    Claude composes the template and runs validate_template, then fixes whatever the validator reports. Large templates are built as drafts.

  4. 04

    It saves version 1

    create_template saves an ordinary template that you can open in the Template Designer. Read it, edit it and run a test before anyone uses it.

Honestly

What Claude can’t do in CheckFlow

  1. 01

    Reach further than you

    Claude is refused wherever its member would be: a step assigned only to someone else, a task behind an incomplete halt, a template you can’t edit.

  2. 02

    Be an assignee

    Tasks are assigned to people and groups. Claude works as you, or as the member its key acts as, never as a separate user.

  3. 03

    Report on analytics

    Cycle times and bottlenecks come from Analytics in the app. The MCP server has no analytics tool.

  4. 04

    See webhook secrets

    Claude can create and replay webhooks, but signing secrets never pass through the conversation.

  5. 05

    Sign in as someone else

    Signing in always connects Claude as you. For an assistant that should act as another member or as the workspace, use an API key.

The MCP server is included on every plan, starting with Business at $10 per user per month, or $9 billed annually, and in the free trial. Claude runs on your Claude plan, so it uses no CheckFlow AI credits.

Claude in practice

Ask, and it happens in CheckFlow.

An example request, the real tool Claude calls, and what it can truthfully say back.

  • Other AI assistants

    The same MCP server works with other clients that sign in or send an API key, such as GitHub Copilot in VS Code.

    Copilot and CheckFlow

  • No Claude? Start here

    The free AI checklist generator drafts a template from one sentence, with no account.

    Try the AI generator

  • The MCP server in depth

    Every tool family, how keys act as a member, and how to keep an assistant safe.

    Read the MCP guide
Claudecheckflow MCP · connectedIllustrative example

Find the Vendor Onboarding checklist for Northwind Traders and tell me what’s left.

checkflow · search_checklistsdone
template:    "Vendor Onboarding"
Vendor name: "Northwind Traders"
→ 1 checklist · InProgress · 14 of 35 tasks complete

Northwind Traders is in Compliance & Risk Assessment, with 14 of 35 tasks done. Sanctions screening is next, assigned to the Compliance group. Shall I list what is left in that phase?

Templates people run with Claude.

Start them, check on them and complete their tasks from a conversation.

Operations & Facilities ManagementLive demo

Vendor Onboarding Process Checklist

7 phases · 35 tasks
Finance & AccountingLive demo

Invoice Approval Workflow Checklist

5 phases · 30 tasks
Information TechnologyLive demo

IT Offboarding Checklist

7 phases · 39 tasks
Browse all templates

Claude and MCP guides

Claude questions

Does CheckFlow work with Claude?

Yes, through the CheckFlow MCP server. Add it as a custom connector in Claude on the web, desktop or mobile, or to Claude Code, and sign in with your CheckFlow account. Claude can then start checklists, complete tasks, fill in fields, build templates and update Data Sets for you.

Can I connect CheckFlow from claude.ai or the Claude mobile app?

Yes. In claude.ai, open Settings, then Connectors, add a custom connector with the CheckFlow MCP server address and click Connect to sign in. A connector added on the web is also available in the Claude mobile apps. On a Team or Enterprise plan, an Owner may need to add it for your organisation first.

Is CheckFlow in Claude’s connector directory?

No. CheckFlow is not listed in Claude’s connector directory. You add it yourself as a custom connector and sign in, using the steps in the connection guide.

What can Claude see in my CheckFlow workspace?

What you can see, and nothing more, when you connect by signing in: Claude works as you, in the workspace you were signed in to. With an API key, it sees what the key’s member can see. Either way its changes are recorded in that person’s name, and it is refused wherever they would be.

Does using Claude with CheckFlow use AI credits?

No. Claude runs on your own Claude plan. The MCP server uses no CheckFlow AI credits; its calls count towards your workspace’s hourly API request budget, shared with the REST API.

Can Claude delete things in CheckFlow?

It can, if its member could. Twenty-six tools are marked destructive, such as deleting a checklist or replacing a Data Set’s records, and Claude asks before running them when its confirmation prompts are on. Keep them on, and if you use an API key, choose one with the least access the job needs.

Can an Administrator stop people connecting Claude?

Yes. Allow AI assistants to connect, on the AI tab of Team Management, switches off every MCP connection for the workspace, and Members need the AI.Assistant permission to connect one. Administrators can revoke any connected assistant on the API & Integrations tab, and only Administrators create API keys.

Give Claude your checklists.

Start a free trial, add CheckFlow as a connector in Claude and sign in. It takes a few minutes.

Start free trialBook a demo

14-day free trial, no credit cardFull refund in your first 30 daysUS hosting, EU on request