Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@paraph-mcp Fill the NDA template with employee_name=Jane Doe and send to jane@example.com for signing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for the Paraph e-signature API. Lets Claude, Cursor, and other MCP-compatible AI tools fill PDFs and send them for signing.
npx paraph-mcpRequires a Paraph API key. Get one free at paraph.dev.
Related MCP server: mcp-server-dashform
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"paraph": {
"command": "npx",
"args": ["-y", "paraph-mcp"],
"env": {
"PARAPH_API_KEY": "dg_your_key_here"
}
}
}
}claude mcp add paraph -- npx -y paraph-mcpThen set PARAPH_API_KEY in your environment.
Add to .cursor/mcp.json:
{
"mcpServers": {
"paraph": {
"command": "npx",
"args": ["-y", "paraph-mcp"],
"env": {
"PARAPH_API_KEY": "dg_your_key_here"
}
}
}
}Tool | Description |
| Get account info including plan and usage |
| List available PDF templates |
| Get template details and field names |
| Fill a PDF and optionally send for signing |
| List requests with optional status filter |
| Get request details and signer progress |
| Cancel a pending signing request |
"List my templates"
"Fill the NDA template with employee_name=Jane Doe and send to jane@example.com for signing"
"Show me all pending signing requests"
"Cancel request abc-123"
MIT
Cancel a pending signing request
Inputs: id (required).
Fill a PDF template and optionally send it for e-signing. Omit signers for fill-only.
Inputs: template_id (required), fields, signers, title, +2 more.
Get account info including plan and usage
Inputs: no named parameters.
Get request details including signer status and signing links
Inputs: id (required).
Get template details including form field names and signer labels
Inputs: id (required).
List signing requests with optional filters
Inputs: page, page_size, status.
List all PDF templates available for filling and signing
Inputs: page, page_size.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool has a clearly distinct purpose targeting specific resources and actions: account info, template operations (get/list), and request operations (create/get/list/cancel). No overlap exists between tools, making it easy for an agent to select the correct one.
All tools follow a consistent verb_noun naming pattern (e.g., get_account, list_templates, create_request). The verbs are appropriate and predictable, with no deviations in style or convention.
With 7 tools, this server is well-scoped for its PDF and e-signing domain. Each tool serves a clear purpose, covering account management, template handling, and request lifecycle without being overly sparse or bloated.
The toolset provides complete CRUD/lifecycle coverage for the domain: account info (get), templates (list/get), and requests (create/get/list/cancel). It supports fill-only and e-signing workflows with no obvious gaps, ensuring agents can handle end-to-end processes.
Hosted MCP server for Anvil — fill & generate PDFs and run Etch e-signature packets for AI agents.
Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents.
MCP server for the PDFGate API. Generate PDFs, manage documents and handle e-signatures.
Send AI-created PDFs for signature, track signers, and return verifiable document evidence.
