Skip to main content
Glama
README.md
# paraph-mcp

MCP server for the [Paraph](https://paraph.dev) e-signature API. Lets Claude, Cursor, and other MCP-compatible AI tools fill PDFs and send them for signing.

## Install

```bash
npx paraph-mcp
```

Requires a Paraph API key. Get one free at [paraph.dev](https://paraph.dev).

## Configure

### Claude Desktop

Add to `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "paraph": {
      "command": "npx",
      "args": ["-y", "paraph-mcp"],
      "env": {
        "PARAPH_API_KEY": "dg_your_key_here"
      }
    }
  }
}
```

### Claude Code

```bash
claude mcp add paraph -- npx -y paraph-mcp
```

Then set `PARAPH_API_KEY` in your environment.

### Cursor

Add to `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "paraph": {
      "command": "npx",
      "args": ["-y", "paraph-mcp"],
      "env": {
        "PARAPH_API_KEY": "dg_your_key_here"
      }
    }
  }
}
```

## Tools

| Tool | Description |
|---|---|
| `get_account` | Get account info including plan and usage |
| `list_templates` | List available PDF templates |
| `get_template` | Get template details and field names |
| `create_request` | Fill a PDF and optionally send for signing |
| `list_requests` | List requests with optional status filter |
| `get_request` | Get request details and signer progress |
| `cancel_request` | Cancel a pending signing request |

## Example prompts

- "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"

## License

MIT

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues