githubEdit

Setup & Configuration

API Endpoints

Environment
MCP Endpoint

Development

https://dev.api.docbits.com/api/mcp/

Stage

https://stage.api.docbits.com/api/mcp/

Production

https://api.docbits.com/api/mcp/

Authentication

All MCP requests require a valid DocBits API key passed as a Bearer token. You can find your API key in Settings > Integration in the DocBits UI.

The token is sent via the Authorization header:

Authorization: Bearer <your-api-key>
circle-exclamation

Client Configuration

Claude Code

Add the DocFlow MCP server using the CLI:

claude mcp add docflow-dev \
  --transport http \
  --header "Authorization: Bearer YOUR_API_KEY" \
  -- https://dev.api.docbits.com/api/mcp/

Or add it to your .claude.json configuration file:

You can also add it to a project-level .mcp.json file:

Claude Desktop

Add the following to your claude_desktop_config.json:

circle-info

On macOS, the config file is at ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows: %APPDATA%\Claude\claude_desktop_config.json.

OpenAI Codex

Codex CLI supports MCP servers. Add to your project configuration:

Generic MCP Client (Python)

For custom integrations using the MCP Python SDK:

Verifying Your Connection

After configuring your client, test the connection by calling the list_workflows tool. It requires no parameters and should return an array of workflows (or an empty array for new organizations).

circle-info

If you get authentication errors, verify that your API key is correct and that the Authorization header is being sent. Some MCP clients require you to restart after changing configuration.

Last updated

Was this helpful?