Hosted (Remote)

Connect to the Check MCP Server without cloning a repository or managing any infrastructure. Check runs the server for you — just point your AI client at the endpoint and log in.

How it works

In hosted mode, Check provides a remote MCP endpoint that your AI client connects to directly. There's nothing to install locally — no Python, no uv, no repository to clone.

• Remote MCP endpoint — A server-side endpoint managed by Check
• Browser-based authentication — Log in through Check Console via OAuth. When your MCP client connects, it initiates an OAuth flow that opens a browser for Console login. You authorize the connection and the client receives a token automatically. No API keys to copy and paste.
• No local dependencies — Works from any machine with an MCP-compatible client
• Same capabilities — Full access to all 270 tools across 18 toolsets, with the same dynamic tool architecture

Endpoint URLs

Start with the sandbox endpoint for testing and development. Switch to the production URL when you're ready to work with live data.

⚠️

Use caution in production. Actions taken through the MCP server are real — payrolls will be processed, payments will be sent, and records will be modified. Consider using read-only mode or toolset filtering to limit what the AI can do.

Connect to an AI client

Choose your client below and follow the configuration instructions. All configurations use the sandbox endpoint — replace the URL with the production endpoint when ready.

Claude Desktop

Open Settings → Developer → Edit Config and add the following to claude_desktop_config.json:

{
  "mcpServers": {
    "check": {
      "type": "url",
      "url": "https://mcp.sandbox.checkhq.com/check/mcp"
    }
  }
}

Restart Claude Desktop after saving. On first use, a browser window will open for you to log in to Check Console and authorize the connection.

Claude Code (CLI)

Run the following command:

claude mcp add --transport http check https://mcp.sandbox.checkhq.com/check/mcp

On first use, Claude Code will open a browser for you to authenticate through Check Console.

Cursor

Open Cursor → Settings → MCP and add the following server configuration:

{
  "mcpServers": {
    "check": {
      "type": "url",
      "url": "https://mcp.sandbox.checkhq.com/check/mcp"
    }
  }
}

On first use, a browser window will open for you to log in to Check Console.

ChatGPT

ChatGPT has native support for remote MCP servers. Go to Settings → Connected apps → Add MCP server and enter:

https://mcp.sandbox.checkhq.com/check/mcp

ChatGPT will handle the OAuth flow automatically.

Google Gemini

Gemini has native support for remote MCP servers. Add the Check MCP endpoint in Gemini's MCP configuration:

https://mcp.sandbox.checkhq.com/check/mcp

Gemini will handle the OAuth flow automatically.

OpenAI Codex CLI

Add the following to ~/.codex/config.json:

{
  "mcpServers": {
    "check": {
      "type": "url",
      "url": "https://mcp.sandbox.checkhq.com/check/mcp"
    }
  }
}

Other MCP clients

For any MCP-compatible client, the general pattern is:

• URL: https://mcp.sandbox.checkhq.com/check/mcp (sandbox) or https://mcp.checkhq.com/check/mcp (production)
• Transport: Streamable HTTP
• Authentication: OAuth 2.0 (your client handles the browser-based flow automatically)

Consult your client's documentation for how to configure remote MCP servers.

Try it out

Once connected, try these example prompts to verify the setup:

• "List all companies in my Check account"
• "Show me the employees for company com_XXXXX"
• "What payrolls are pending approval?"
• "Give me a summary of the most recent payroll run"
• "What tools are available for managing tax settings?"

Access control

You can restrict what the MCP server can do using HTTP headers. Pass these headers from your MCP client to control tool availability per session.

Read-only mode

Disable all write operations (create, update, delete, approve, etc.):

X-MCP-Readonly: true

Limit to specific toolsets

Only expose certain categories of tools:

X-MCP-Toolsets: companies,employees

Available toolsets: bank_accounts, companies, compensation, components, contractor_payments, contractors, documents, employees, external_payrolls, forms, payments, payroll_items, payrolls, platform, tax, webhooks, workflows, workplaces

Exclude specific tools

Block individual tools by name:

X-MCP-Exclude-Tools: create_bank_account,delete_employee

Combining options

All access control options can be combined. Filtering precedence: exclude_tools > read_only > tools > toolsets.

Switching environments

To switch between sandbox and production, update the URL in your client configuration: