CheckFlow

CheckFlow MCP Server

The official MCP server for CheckFlow, the checklist and process software. Connect an AI assistant to your CheckFlow workspace and ask in plain language: start a checklist, tell me what is overdue, fill in this task, turn this procedure into a template.

The server is hosted by CheckFlow. There is nothing to install or run: you add the address below to your MCP client and sign in with your CheckFlow account, or send an API key. This repository holds the documentation and the server.json published to the MCP Registry; the server's code is not open source.

What you can ask for

The assistant runs on its own provider's AI, not CheckFlow's, so it uses none of your workspace's AI credits.

Two ways to connect

• Sign in with your CheckFlow account. The client opens CheckFlow in your browser, you sign in and choose Allow, and the assistant then works as you. There is no key to copy or store. This is the only way to connect claude.ai, Claude Desktop's Connectors screen, the Claude mobile apps and ChatGPT.
• An API key, sent in the X-API-KEY header. This is for clients that cannot sign in, for an assistant that should act as somebody other than you or as the workspace, and for scripts.

Before you start

1. Use your region's address. Workspaces in the United States use https://api.checkflow.io/mcp; workspaces in Europe use https://api-eu.checkflow.io/mcp. A request to the other region is refused with WRONG_REGION, and the message names the right address.
2. Check you're allowed to connect. An Administrator can turn off Allow AI assistants to connect on the AI tab of Team Management; it is on unless someone has turned it off. Members need the AI.Assistant permission, which new Members are given and an Administrator can grant or remove on the Users tab. Administrators don't need it. Guests can't connect an assistant.
3. For an API key only: an Administrator creates keys on the API & Integrations tab of Team Management. For a personal assistant, create a key that acts as you. See Creating an API key. You don't need a key to sign in.

The examples use the United States address; use the Europe address if your workspace is in Europe.

Signing in

1. Your browser opens a CheckFlow page that names the assistant asking to connect.
2. Sign in the way you normally do: with your email and password, with Google or Microsoft, or with your company's single sign-on. For single sign-on, enter your workspace's address (for example acme for acme.checkflow.io) and CheckFlow sends you to your company's sign-in page.
3. CheckFlow shows what the assistant will be able to do, which workspace it is for and the address it will send you back to. Check them, then click Allow.
4. Your browser returns to the assistant, which is now connected.

The assistant works as you, in the workspace you were signed in to. If you belong to more than one workspace, switch to the right one in CheckFlow before you connect; to connect another workspace too, add the server a second time and connect it while that workspace is selected. The connection lasts until you or an Administrator disconnects it, or until it goes unused for 30 days. It also stops working if you leave the workspace or are made a Guest.

Connect a client

Claude (web, desktop and mobile)

1. In Claude, open Settings, then Connectors, and choose Add custom connector.
2. Name it CheckFlow, enter your server address, and add it.
3. Click Connect and sign in.

A connector you add on the web is also available in the Claude Desktop and mobile apps. On a Team or Enterprise plan, an Owner may need to add the connector for your organisation before members can connect it.

ChatGPT

ChatGPT connects to a custom MCP server in developer mode. Follow OpenAI's instructions for connecting a remote MCP server, give it your server address, and choose OAuth as the authentication. ChatGPT finds CheckFlow's sign-in page on its own, so there is nothing else to configure. Then sign in.

Claude Code

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

Then, in Claude Code, run /mcp, choose checkflow and Authenticate. Your browser opens so that you can sign in.

To connect with an API key instead, add the header:

claude mcp add --transport http checkflow https://api.checkflow.io/mcp --header "X-API-KEY: your-api-key-here"

Add --scope user to either command to make the server available in every project, rather than only the current one. Run claude mcp list to check that it connected, then ask Claude something like "List my CheckFlow templates."

Cursor

Add the server to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json in one project. With only the address, Cursor offers to sign you in when you enable the server:

{

"mcpServers": { "checkflow": { "url": "https://api.checkflow.io/mcp" } } }

To use an API key instead, add a headers entry:

{

"mcpServers": { "checkflow": { "url": "https://api.checkflow.io/mcp", "headers": { "X-API-KEY": "your-api-key-here" } } } }

Open Cursor's MCP settings to check that the server shows as connected and its tools are listed.

Visual Studio Code

Add the server to .vscode/mcp.json in your workspace. With only the address, VS Code asks you to sign in when the server starts:

{

"servers": { "checkflow": { "type": "http", "url": "https://api.checkflow.io/mcp" } } }

To use an API key instead, add an inputs block, which makes VS Code prompt for the key once and store it securely rather than keeping it in the file:

{

"inputs": [ { "type": "promptString", "id": "checkflow-api-key", "description": "CheckFlow API key", "password": true } ], "servers": { "checkflow": { "type": "http", "url": "https://api.checkflow.io/mcp", "headers": { "X-API-KEY": "${input:checkflow-api-key}" } } } }

Start the server from the file or the MCP: List Servers command, then use the tools from Copilot Chat in agent mode.

Claude Desktop with an API key

Claude Desktop's Connectors screen signs in, as described above. To connect Claude Desktop with an API key instead, use the mcp-remote bridge, which needs Node.js 18 or later. Open Settings, then Developer, and click Edit Config. Add a checkflow entry under 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" } } } }

Save the file and restart Claude Desktop. Write the header as X-API-KEY:${CHECKFLOW_API_KEY} with no space after the colon: some platforms split arguments on spaces, which would break the header.

Configuration files are often synced, backed up or shared. Where a client supports environment variables or a secret prompt, use them rather than pasting an API key into the file. Signing in avoids storing a key at all.

MCP Inspector

MCP Inspector lets you explore the tools and call them by hand. It is the quickest way to check a key.

1. Run npx @modelcontextprotocol/inspector.
2. Choose the Streamable HTTP transport and enter https://api.checkflow.io/mcp.
3. Add a custom header named X-API-KEY with your key.
4. Click Connect, then List Tools.

Other clients

Any client works if it can connect to a remote MCP server over Streamable HTTP, and either:

• signs in using the MCP authorization specification (OAuth 2.1), or
• sends an API key with every request, in the X-API-KEY header or as Authorization: Bearer your-api-key-here.

The Authorization: Bearer form is for clients that can send a bearer token but not a custom header, such as the MCP connector in the Claude API and Microsoft 365 agent connectors. If a request carries both headers, X-API-KEY is used.

CheckFlow only sends a sign-in back to the addresses of the assistants it supports: Claude, Claude Code, ChatGPT, VS Code, Cursor, Microsoft 365 Copilot, and other desktop applications that receive the sign-in on your own computer. If a client's sign-in page says CheckFlow does not send sign-ins to its address, connect it with an API key, or ask support to add the client.

More step-by-step guides are on checkflow.io: Claude and Copilot.

Disconnecting an assistant

• One you connected by signing in: open My Profile & Settings from the menu under your name, go to the AI Assistants tab and click Disconnect next to it. Removing the connector in the assistant also ends the connection.
• Any member's assistant, as an Administrator: on the API & Integrations tab of Team Management, find it under Connected AI assistants and revoke it.
• One that uses an API key: an Administrator revokes the key on the API & Integrations tab.
• Every assistant at once: an Administrator turns off Allow AI assistants to connect on the AI tab. The REST API is not affected.

Check the connection

Ask your assistant: "Which CheckFlow workspace are you connected to?" It answers from get_workspace_info, which returns the workspace's name, region, members, groups, tags and templates.

| The sign-in page says Guests cannot connect AI assistants. | You are a Guest in this workspace. | Ask an Admini