Use flatmark from Claude Code, Cursor and other MCP clients

The flatmark MCP server gives agents three tools to convert documents. They use the same API key and credits as the REST API.

Last updated

flatmark runs an MCP server at https://api.flatmark.dev/mcp/ over streamable HTTP. An agent gets three tools for converting documents.

Tool What it does Credits with a key
convert_document Direct call: a base64 file and its filename in, Markdown out 1
submit_conversion_job Queue: returns a job ID (API key required) 10, refunded if the job fails
get_conversion_job Job status; Markdown inline under 100 KB, otherwise a download path 0

Without a key, convert_document runs anonymously within the rate limit. The queue tools need a key. The tools return Markdown only. The JSON structure file comes from the REST API.

Claude Code

claude mcp add --transport http flatmark https://api.flatmark.dev/mcp/ \
  --header "X-API-Key: YOUR_KEY"

Cursor

Add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for all projects:

{
  "mcpServers": {
    "flatmark": {
      "url": "https://api.flatmark.dev/mcp/",
      "headers": {"X-API-Key": "YOUR_KEY"}
    }
  }
}

Claude Desktop and claude.ai

Custom connectors there take a URL but no API key header. The tools then run anonymously: convert_document works, the queue tools do not.

Next step

Sign in with a magic link and create the API key for your agent's X-API-Key header.

FAQ

Does the MCP server need an API key?
Not for convert_document, which runs anonymously within the rate limit. submit_conversion_job and get_conversion_job need a key.
What does each tool cost?
With a key, convert_document costs 1 credit. submit_conversion_job costs 10, refunded if the job fails. get_conversion_job costs nothing.