Connect your agent

anyformat speaks MCP, so the agent you already use can parse documents, build workflows and read results without you writing any code. One endpoint, one key, one config block per client.


URL	`https://api.anyformat.ai/mcp`
Transport	Streamable HTTP
Auth	`Authorization: Bearer <your af_... key>`

Mint a key at app.anyformat.ai/api-key and export it before you start. The same key works on the REST API.

export ANYFORMAT_API_KEY="af_..."

Pick your client

One command, and --scope user makes it available in every project:

claude mcp add --transport http anyformat https://api.anyformat.ai/mcp \
  --header "Authorization: Bearer $ANYFORMAT_API_KEY" --scope user

Or commit it to the project by writing .mcp.json in the repository root. Claude Code expands ${VAR} from the environment, so the key stays out of the file:

{
  "mcpServers": {
    "anyformat": {
      "type": "http",
      "url": "https://api.anyformat.ai/mcp",
      "headers": { "Authorization": "Bearer ${ANYFORMAT_API_KEY}" }
    }
  }
}

Confirm with claude mcp list.

Add the server from the command line:

codex mcp add anyformat --url https://api.anyformat.ai/mcp

Then put the header in ~/.codex/config.toml. env_http_headers reads the value from the named environment variable, so the key is never written to the file:

[mcp_servers.anyformat]
url = "https://api.anyformat.ai/mcp"
env_http_headers = { "Authorization" = "ANYFORMAT_MCP_AUTH" }

export ANYFORMAT_MCP_AUTH="Bearer $ANYFORMAT_API_KEY"

Confirm with codex mcp list, then restart Codex. A project-scoped .codex/config.toml works the same way in a trusted project.

Add the server to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one. Cursor expands ${env:VAR}:

{
  "mcpServers": {
    "anyformat": {
      "url": "https://api.anyformat.ai/mcp",
      "headers": { "Authorization": "Bearer ${env:ANYFORMAT_API_KEY}" }
    }
  }
}

Add it to opencode.json as a remote server. OpenCode interpolates {env:VAR}:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "anyformat": {
      "type": "remote",
      "url": "https://api.anyformat.ai/mcp",
      "enabled": true,
      "headers": { "Authorization": "Bearer {env:ANYFORMAT_API_KEY}" }
    }
  }
}

A host that can only launch a local stdio process reaches the endpoint through a bridge. mcp-remote is the Node one. Put the header value in an environment variable so the space in Bearer ... survives argument parsing:

{
  "mcpServers": {
    "anyformat": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.anyformat.ai/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": { "AUTH_HEADER": "Bearer af_..." }
    }
  }
}

fastmcp-remote is the Python equivalent, run with uvx. It takes the header as one argument, so it needs no environment variable:

uvx fastmcp-remote https://api.anyformat.ai/mcp \
  --header "Authorization: Bearer $ANYFORMAT_API_KEY"

Both bridges skip their own OAuth flow when you give them an Authorization header. For Claude Desktop the file is claude_desktop_config.json, under Settings → Developer.

Any MCP host that lets you set a header on a streamable HTTP server will work. This handshake is the whole contract:

curl -X POST https://api.anyformat.ai/mcp \
  -H "Authorization: Bearer $ANYFORMAT_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

The Custom connectors panel in Claude on the web, in Cowork and in Claude Desktop expects a remote server that speaks OAuth. anyformat authenticates with an API key header and has no OAuth flow today, so connect it from a client that can set a header, or through one of the stdio bridges above.

Check it worked

Ask the agent something only anyformat can answer:

“List my anyformat workflows.”

If the key is wrong you get an authentication error rather than an empty list. If the tools are missing entirely, the host has not reloaded its config: restart it.

The first three things to ask

“Parse invoice.pdf with anyformat and save the markdown to invoice.md.”

“Build an anyformat workflow that pulls the invoice number, the total and the due date, then run every PDF in ./inbox through it and write the results to a CSV.”

“Which of my anyformat runs failed yesterday, and why?”

The agent stages the local file, creates the workflow, runs the documents and polls until each run is terminal. Agents over MCP walks one real session call by call.

What the agent can reach

Sixteen tools, split by what your key is allowed to do. A key with read scope only never sees the tools that write: they are absent from the tool list rather than failing when called.

Group	Tools
Workflows	list, get, create, update, delete, list versions
Documents	stage files, upload documents, run a packet, get a packet, list packets, delete
Runs	get a run, list runs
Reading	parse a document, ask the knowledge base

The MCP server reference has the full table, the scopes and the error shapes.

Not using an agent?

The Claude Code skill teaches Claude the workflow API without MCP, and the SDKs do the same job from your own code.

Get started

Nodes

Workflows

Schema & fields

Documents

Outputs & integrations

Health

Billing

Connect your agent

Pick your client

Check it worked

The first three things to ask

What the agent can reach

Not using an agent?

Next steps

Agents over MCP

MCP server reference

​Pick your client

​Check it worked

​The first three things to ask

​What the agent can reach

​Not using an agent?

​Next steps

Agents over MCP

MCP server reference

Pick your client

Check it worked

The first three things to ask

What the agent can reach

Not using an agent?

Next steps