MCP Server

Connect Plume to AI assistants like Claude using the Model Context Protocol.

The Plume MCP server lets AI agents manage contacts, upload documents, place signature blocks, and send documents for signing — all through natural language.

Connection URL

https://plume.claap.io/api/mcp

This is the only URL you need. Authenticate requests with your API key as a Bearer token.

Setup

Get your API key

Go to Settings > API Keys and generate a new key. Copy it — you won't see it again.

Add the MCP server to your AI client

Choose your client below and add the configuration.

Client Configuration

Claude Desktop

Open Settings > MCP Servers, click "Add", and choose "Streamable HTTP".

Field	Value
URL	`https://plume.claap.io/api/mcp`
Header name	`Authorization`
Header value	`Bearer sk_live_your_key_here`

Or add it manually to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "plume": {
      "type": "streamable-http",
      "url": "https://plume.claap.io/api/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_your_key_here"
      }
    }
  }
}

Claude Code (CLI)

Add to your project's .claude/settings.json:

{
  "mcpServers": {
    "plume": {
      "type": "streamable-http",
      "url": "https://plume.claap.io/api/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_your_key_here"
      }
    }
  }
}

Cursor

Open Settings > MCP, click "Add new MCP server", and select "Streamable HTTP".

Field	Value
Name	`plume`
URL	`https://plume.claap.io/api/mcp`

Then add the authorization header in the JSON config:

{
  "mcpServers": {
    "plume": {
      "url": "https://plume.claap.io/api/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_your_key_here"
      }
    }
  }
}

Other MCP Clients

Any client that supports the Model Context Protocol with Streamable HTTP transport can connect. You need:

Parameter	Value
Transport	Streamable HTTP
URL	`https://plume.claap.io/api/mcp`
Auth header	`Authorization: Bearer sk_live_your_key_here`

You can verify the connection with curl:

curl -X POST https://plume.claap.io/api/mcp \
  -H "Authorization: Bearer sk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Available Tools

Contacts

create_contact

Create a new contact for use as a signatory. Returns the existing contact if the email already exists.

name required: Full name of the contact
email required: Email address (must be valid)
company optional: Company name

search_contacts

Search for existing contacts by name or email.

query optional: Search term to filter contacts. Returns all contacts if omitted.

Documents

upload_document

Upload a PDF document to Plume from a URL.

file_url required: Public URL to download the PDF from (http/https). Max file size: 50 MB.

list_documents

List documents in your workspace with optional status filtering.

status optional: Filter by status: draft, pending, partially_signed, completed, canceled

get_document_status

Get the current status of a document including signatory progress.

document_id required: The document ID

Signature Blocks

place_blocks

Place signature, paraphe (initials), or text blocks on a document. Blocks are assigned to signatories by email.

document_id required: The document ID
blocks required: Array of blocks, each with: type (signature | paraphe | text), page, x, y (coordinates in percentage), signatory_email, and optional width / height

Signing

send_document

Send a prepared document for signing. Emails are sent to all signatories with their signing links.

document_id required: The document ID (must be in draft status with at least one block placed)

download_signed_pdf

Get the download URL for a signed PDF once all signatories have completed signing.

document_id required: The document ID (must be in completed status)

Example Conversation

Once connected, you can ask your AI assistant things like:

> Upload the NDA at https://example.com/nda.pdf and send it
  to alice@acme.com for signature

> What documents are currently pending?

> Check if the contract I sent to bob@example.com has been signed yet

> Download the signed version of document abc-123

Typical Workflow

Step	Tool	What happens
1	`create_contact`	Register the signatory (skipped if they already exist)
2	`upload_document`	Upload the PDF — document starts in `draft` status
3	`place_blocks`	Place signature/paraphe blocks at the right coordinates
4	`send_document`	Send signing emails — status moves to `pending`
5	`get_document_status`	Monitor signing progress
6	`download_signed_pdf`	Download once `completed`

Troubleshooting

Connection errors

Verify your API key is valid by testing with curl:

curl -X POST https://plume.claap.io/api/mcp \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools not showing up

Restart your AI client after adding the MCP configuration. Most clients require a restart to discover new servers.

Permission errors

API keys are scoped to the workspace of the user who created them. Make sure the key has access to the documents you're trying to manage.

Need help? Contact tech@claap.io · REST API Docs