paraph-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARAPH_API_KEY | Yes | Your Paraph API key. Get one free at https://paraph.dev. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountB | Get account info including plan and usage |
| list_templatesC | List all PDF templates available for filling and signing |
| get_templateB | Get template details including form field names and signer labels |
| create_requestA | Fill a PDF template and optionally send it for e-signing. Omit signers for fill-only. |
| list_requestsC | List signing requests with optional filters |
| get_requestB | Get request details including signer status and signing links |
| cancel_requestC | Cancel a pending signing request |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.