MCP server for PDF forms

Agents can hand a PDF to Snapfritz and get back a link where a person reviews the fields and signs. The server speaks stateless Streamable HTTP and authenticates with the same API key as the REST API. Signing is deliberately not a tool.

Endpoint: POST https://snapfritz.com/mcp
Auth: Authorization: Bearer sf_live_…
Plan: Platin
Discovery: /.well-known/mcp.json

Tools

Tool	Scope	Purpose
`submit_pdf`	`documents:write`	PDF by URL or base64. Returns id, fields and review_url.
`get_document`	`documents:read`	Status, fields and a fresh review link.
`list_documents`	`documents:read`	Newest first, optional status, limit 1–100.
`get_forward_address`	`documents:write`	The account's forwarding address.

Example for Cursor and Claude Desktop

Create a key under Settings → Developer. Claude Code:

claude mcp add --transport http snapfritz https://snapfritz.com/mcp \
  --header "Authorization: Bearer $SNAPFRITZ_API_KEY"

{
  "mcpServers": {
    "snapfritz": {
      "url": "https://snapfritz.com/mcp",
      "headers": { "Authorization": "Bearer sf_live_…" }
    }
  }
}

Limits

GET and DELETE answer 405. There is no session and no SSE stream.
URL fetches are HTTPS only, with no private or link-local addresses, 20 MB at most.
60 requests and 10 uploads per minute per key, in one instance's memory. Allowance used up: nothing extra is charged.
A read-only key gets the normal document page, which needs a sign-in. Only write mints the sign-in-free review link, 7 days, this document only.

Can the agent sign?

No. There is no sign tool. A person opens the review link.

Which plan?

The API and MCP belong to the Platin plan (99 EUR net per month, 100 finished forms per month).

Does OAuth work?

No. Bearer key only. Clients that can only do OAuth cannot connect.

REST API · OpenAPI