The Formify MCP Server implements the Model Context Protocol — a standard that lets AI assistants connect to external services. With the Formify MCP server, AI assistants can securely access your Formify account to create and manage documents and drafts, inspect templates and fields, track signing progress, send reminders, and manage related account/webhook operations.

MCP server URL

https://mcp.formify.eu/mcp

How it works

The MCP server acts as a bridge between your AI client and the Formify API. OAuth authentication happens directly between your AI client and Formify's authorization server. The MCP server validates the token on each request and proxies tool calls to the Formify API. Each user authorizes access with their own Formify account.

1
Add the MCP server URL to your AI client
2
Complete the Formify login when prompted
3
Start using natural language to manage e-signing

Quick start

Claude (Desktop & Web)

  1. Go to Customize → Connectors → Add custom connector.
  2. Enter the server URL: https://mcp.formify.eu/mcp
  3. Click Add, then Connect.
  4. Sign in to your Formify account and select Allow access.
  5. Verify the connection by entering a prompt such as: "List my templates."

Claude Code (CLI)

  1. Launch Claude Code in your terminal or VS Code extension.
  2. Run /mcp add formify https://mcp.formify.eu/mcp
  3. When prompted, complete the Formify login in your browser.
  4. Verify with: "List the available Formify MCP tools."

Cursor, Windsurf, VS Code, Codex and other clients

Remote MCP configuration differs between clients and client versions. Use the server URL below and follow your client's own MCP configuration documentation:

https://mcp.formify.eu/mcp

What you can do

Once connected, you can use natural language to manage the full document signing lifecycle:

Example prompts

Available tools

Documents

Tool Description
list_documentsList documents on the account
get_documentGet document status and signee details
create_documentCreate a document from a template or uploaded PDF and send it for signing
revoke_documentRevoke an unsigned document
delete_documentPermanently delete a completed or revoked document
get_signed_document_urlGet a time-limited download link for a signed document (valid 10 minutes)
send_reminderSend a signing reminder to unsigned signees
update_signeeCorrect a signee's name, email, or phone number

Drafts

Tool Description
list_draftsList drafts with pagination
get_draftGet full draft configuration
create_draftCreate a new draft
update_draftReplace an existing draft's configuration
get_draft_fileGet the draft preview PDF as an embedded resource
get_draft_file_urlGet a one-time download URL for the draft preview PDF
send_draftConvert a draft to a live document and send invitations
delete_draftPermanently delete a draft

Files

Tool Description
request_file_upload_urlGet a presigned upload URL for a PDF file attached to the conversation
upload_fileUpload a PDF by presigned upload ID, public URL, or base64 content
get_file_fieldsList form fields in an uploaded PDF before creating a document
merge_filesMerge 2–8 uploaded PDFs into a single file (page order follows input order)
delete_fileDelete a previously uploaded file

Templates & form fields

Tool Description
list_templatesList available signing templates
get_templateGet template details, signee slots, and signature settings
get_template_fieldsList form fields in a template (types, options, editability)
get_document_fieldsList form fields in a created document
get_document_field_valuesGet current field values in a document
set_document_field_valuesUpdate form field values on an existing document

Webhooks

Tool Description
list_webhooksList registered webhooks
register_webhookRegister a webhook for signing events
delete_webhookDelete a webhook
rotate_webhook_secretRotate the HMAC signing secret for a webhook

Account & user

Tool Description
get_account_usersList users on the account
get_account_capabilitiesCheck enabled features (BankID, WhatsApp, AI assistant, etc.)
get_current_userGet the authenticated user's info

Authentication & permissions

The MCP server uses OAuth 2.0 with PKCE. No API keys or secrets are needed — just sign in to your Formify account when prompted.

When you connect, you authorize the AI client to perform actions on your behalf within your existing Formify account permissions:

There are two independent session layers:

You can revoke access at any time under Settings → Integration → My applications.

Privacy

The MCP server holds no persistent storage. During an active session, the OAuth access token and user ID are kept in process memory to authenticate requests to the Formify API. When a PDF file is uploaded via the MCP server, the file is held temporarily in memory until it has been forwarded to the Formify API — typically a matter of seconds — and is then discarded. Draft preview PDFs fetched via get_draft_file follow the same pattern — held in memory for the duration of the request only, never persisted. No file data is written to disk or retained after the request completes.

The MCP server acts as a proxy: document metadata, form values and PDF previews transit through process memory only while a request is being fulfilled, are never written to disk, and are not retained afterwards. Full details in the Formify Privacy Policy.

AI model visibility: When you fetch documents via the MCP server, their contents — including titles, recipient names, and email addresses — are sent to the AI model as part of the conversation context. Be aware that personal data may be processed by your AI provider.

Limitations

Support

For questions or issues with the MCP integration: support@formify.eu