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 trial Connecting 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 \
  --header "X-API-KEY: your-api-key-here"

Check it connected

claude mcp list
# then ask: "List my CheckFlow templates."

Add --scope user to use it in every project. EU workspaces use api-eu.checkflow.io.

In short

Last updated October 2026

Claude connects to CheckFlow through the CheckFlow MCP server. It can then read your Tasks Grid, start checklists, fill in fields, complete tasks and build templates, as the member whose API key it holds. Claude Code connects directly and Claude Desktop through the mcp-remote bridge. Claude on the web and on mobile need OAuth, which CheckFlow doesn’t support yet, unless your organisation is in Anthropic’s request-headers beta.

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 signs in with an API key sent in an X-API-KEY header. It doesn’t support OAuth yet. So the question for each Claude app is whether it can send that header.

How each Claude app connects to the CheckFlow MCP server, as at October 2026
Claude app	Connects?	How
Claude Code	Yes	claude mcp add with the --header option
Claude Desktop	Yes	The mcp-remote bridge in the developer config (needs Node.js 18 or later)
Claude on the web, and Desktop’s Connectors screen	Only with Anthropic’s beta	A custom connector with No sign-in and an x-api-key request header. Request headers are a beta for a limited set of organisations
Claude mobile apps	Only with Anthropic’s beta	Uses a connector added on the web, so the same limit applies
Claude API (MCP connector)	No	It sends an OAuth bearer token, not a custom header

CheckFlow is not in Claude’s connector directory. On Team and Enterprise plans, a connector with a request header shares one key, so everyone using it would act as that one CheckFlow member. Claude Code or Desktop with a personal key keeps changes in each person’s name.

Claude Desktop

Set up Claude Desktop

Ask an Administrator for an API key that acts as you, created on the API & Integrations tab of Team Management. 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

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.
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.
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.
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

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.
02
Be an assignee
Tasks are assigned to people and groups. Claude acts as the member whose key it holds, never as a separate user.
03
Report on analytics
Cycle times and bottlenecks come from Analytics in the app. The MCP server has no analytics tool.
04
See webhook secrets
Claude can create and replay webhooks, but signing secrets never pass through the conversation.
05
Connect from claude.ai for most people
Until CheckFlow supports OAuth, the web and mobile apps can connect only for organisations in Anthropic’s request-headers beta.

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 any client that can send a custom header, 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. Claude Code connects directly with an API key in a header, and Claude Desktop connects through the mcp-remote bridge. 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?

Not yet for most people. Those apps sign in to connectors with OAuth, which the CheckFlow MCP server doesn’t support yet. Organisations in Anthropic’s request-headers beta can add a custom connector with an x-api-key header; everyone else can use Claude Code or Claude Desktop today.

Is CheckFlow in Claude’s connector directory?

No. CheckFlow is not listed in Claude’s connector directory. You connect it yourself with an API key, using the steps in the connection guide.

What can Claude see in my CheckFlow workspace?

What the member its API key acts as can see, and nothing more. For a personal assistant, use a key that acts as you. Claude’s changes are recorded in that member’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 use a key 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. Only Administrators create API keys, and a key can be revoked at any time.

Give Claude your checklists.

Start a free trial, create an API key that acts as you and connect Claude Code or Claude Desktop in minutes.

Start free trial Book a demo

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

The Claude checklist integration that works in your name.

Ask Claude, and the work happens in CheckFlow.

No switching tabs

Procedures become templates

Still accountable

Which Claude apps can connect

Set up Claude Desktop

What Claude can do in CheckFlow

Your work

Start checklists

Complete tasks

Find what’s stuck

Keep lists current

Set up schedules

How Claude turns a procedure into a template

It reads your workspace

It reads the rules

It drafts and checks

It saves version 1

What Claude can’t do in CheckFlow

Reach further than you

Be an assignee

Report on analytics

See webhook secrets

Connect from claude.ai for most people