Build ((automated signing flows)). Powered by ((natural language)).
Connect any AI assistant to Formify in 30 seconds. Send contracts, track status, and orchestrate post-signing workflows — all from a single prompt. Or build it your way with the REST API.
Plug Formify into any AI assistant.
The Formify MCP server lets AI clients securely create documents, upload PDFs, track signing, and manage webhooks — using your own Formify account. No API keys. Just OAuth and one URL.
1
Add the server
Drop our URL into your AI client's MCP config.
2
Sign in
Send, track, automate — all from natural language.
3
Start prompting
Send, track, automate — all from natural language.
One prompt. Everything from sending to ((post-signing)).
The MCP server exposes 28 tools across documents, files, templates, webhooks, and account operations. You don't have to remember any of them — just describe what you want.
"Send the NDA template to anna@acme.com for signing."
"Has the contract with Erik been signed yet? If not, send a reminder."
"Merge these two PDFs and send for signing."
"Revoke the unsigned offer I sent
yesterday."
"Set up a webhook to notify me when documents are completed."
"Download the signed copy of the employment agreement."
Drop-in skills for ((common signing flows)).
We've packaged the workflows our customers ask for most often as open Claude skills. Download, install, and use them as-is — or customize them for your own templates and integrations.
tink-* attributes for BankID, ID scan, SMS PIN, and more. Build from scratch or add fields to existing PDFs.tink-* attributes for BankID, ID scan, SMS PIN, and more. Build from scratch or add fields to existing PDFs.tink-* attributes for BankID, ID scan, SMS PIN, and more. Build from scratch or add fields to existing PDFs.More skills are on the way.
We're building skills around the workflows our customers run most.
Turn any PDF field into a ((verified, validated input)) with tink-* attributes.
Formify reads your PDF form field names. Add pipe-separated tink-* attributes and ordinary text fields become BankID-verified identity, SMS PIN codes, ID scans, auto-populated company data, and more.
How it works
tink-* attribute. Multiple attributes on the same field are combined; for example, format validation plus PIN verification plus transparent styling all on one input.A clean REST API. OAuth 2.0. OpenAPI 3.x.
Every MCP tool maps to a REST endpoint. Self-service OAuth via Client ID Metadata Document or Dynamic Client Registration. Webhooks with HMAC signing. Full OpenAPI spec, Markdown reference, and llms.txt for AI consumption.
