mcpField
F
Formfeed

Formfeed

Remote
docs.formfeed.devProductivity1Updated today
RepositoryVisit website

About Formfeed

Formfeed’s MCP server lets agents work with document templates, validate data, render PDFs and images, and convert office documents to PDF. It supports offline validation and invoice checks, while template changes are saved as drafts for a person to publish.

Key features

  1. 01List templates and inspect their schemas
  2. 02Validate template data, including offline HTML
  3. 03Check ZUGFeRD and Factur-X invoice data
  4. 04Render PDFs or images from templates
  5. 05Convert Office and OpenDocument files to PDF
  6. 06Save template changes as drafts

Use cases

  1. 01Validate data before rendering a document
  2. 02Check an e-invoice against EN 16931
  3. 03Generate a PDF or inspect a rendered image
  4. 04Convert a Word, Excel, or PowerPoint file to PDF

MCP support

Provides ten tools to MCP clients over stdio or hosted Streamable HTTP. Authentication can use an API key or Formfeed account sign-in; without a key, offline validation tools remain available.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.formfeed.dev/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://mcp.formfeed.dev/mcpAuth required
Streamable HTTPhttps://mcp.formfeed.dev/mcp/{workspace_id}
Packages
npm@formfeed/mcp0.3.21

Tools

Details

From the project README

@formfeed/mcp

formfeed MCP server – quality and maintenance score on Glama

Model Context Protocol server for Formfeed. Gives Claude, Cursor and other agents ten tools: list_templates, get_template_schema, validate_template (free: the data against the template's schema, ad-hoc HTML offline), check_invoice (free and offline: the _invoice block of a ZUGFeRD / Factur-X e-invoice against EN 16931), render (with einvoice, the PDF becomes that e-invoice; an image comes back as a picture the agent can look at), convert_to_pdf (Word, Excel, PowerPoint and OpenDocument to PDF), get_render, get_workspace (which workspace the server works in, and the units left), get_template_source and save_template (a new template or a change as a draft, which a person publishes in Formfeed; needs template:write on the key, or the person's permission for a signed-in agent).

stdio (Claude Desktop, Cursor, Claude Code)

{
  "mcpServers": {
    "formfeed": {
      "command": "npx",
      "args": ["-y", "@formfeed/mcp"],
      "env": { "FORMFEED_API_KEY": "ff_test_…" }
    }
  }
}

A test key renders for free (on the Free plan with a test mark); a live key consumes units. Without FORMFEED_API_KEY the server starts too, with the offline checks only: validate_template with html and engine, and check_invoice. FORMFEED_REGION=us or FORMFEED_BASE_URL select another API host.

Hosted (Streamable HTTP)

https://mcp.formfeed.dev/mcp takes Authorization: Bearer ff_…, or signs in with your Formfeed account when no key is sent (OAuth; the client opens the browser, and you choose the workspace the agent works in). https://mcp.formfeed.dev/mcp/<workspace id> pins another workspace for a signed-in client. Self-host the same endpoint with formfeed-mcp --http --port 8790, plus --auth-server <issuer> for OAuth sign-in against your own Supabase Auth.

Claude Code installs the hosted server together with two skills for writing and checking templates as Formfeed's plugin, from formfeed-dev/skills: https://docs.formfeed.dev/devkit/coding-agents

Documentation: https://docs.formfeed.dev/integrations/mcp

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.