@signatrust/mcp-server

Send and verify e-signatures from Claude — zero-custody, with independently verifiable cryptographic evidence for every signature.

Model Context Protocol (MCP) server for the SignaTrust document signing API. Enables AI assistants like Claude to create envelopes, manage templates, check signing status, and verify blockchain anchors via natural language.

Quick Start

Claude Code

claude mcp add signatrust -- npx -y @signatrust/mcp-server

Then set your API key in the MCP server environment.

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "signatrust": {
      "command": "npx",
      "args": ["-y", "@signatrust/mcp-server"],
      "env": {
        "SIGNATRUST_API_KEY": "sk_live_your_key_here"
      }
    }
  }
}

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

{
  "mcpServers": {
    "signatrust": {
      "command": "npx",
      "args": ["-y", "@signatrust/mcp-server"],
      "env": {
        "SIGNATRUST_API_KEY": "sk_live_your_key_here"
      }
    }
  }
}

VS Code

Add to .vscode/mcp.json (note the top-level key is servers, not mcpServers):

{
  "servers": {
    "signatrust": {
      "command": "npx",
      "args": ["-y", "@signatrust/mcp-server"],
      "env": {
        "SIGNATRUST_API_KEY": "sk_live_your_key_here"
      }
    }
  }
}

To keep the key out of the file, use an input prompt instead of env:

{
  "inputs": [
    { "id": "signatrust-key", "type": "promptString", "description": "SignaTrust API key", "password": true }
  ],
  "servers": {
    "signatrust": {
      "command": "npx",
      "args": ["-y", "@signatrust/mcp-server"],
      "env": { "SIGNATRUST_API_KEY": "${input:signatrust-key}" }
    }
  }
}

Available Tools

Three-tier security. create_envelope accepts securityLevel: STANDARD (bearer token only), VERIFIED (adds SMS/email OTP — recommended for employment, vendor, or healthcare consent), or CERTIFIED (adds WebAuthn biometric + device binding — recommended for real estate, high-value, or regulatory signings).

API Key Scopes

Create an API key at Settings > API Keys in your SignaTrust dashboard. Assign scopes based on what tools you need:

Environment Variables

Natural Language Examples

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

• "List all my pending envelopes"
• "Upload ~/Documents/nda.pdf and send it to alice@example.com with VERIFIED security"
• "Show me available templates, then create a lease agreement from the residential template for John Doe"
• "Check the blockchain verification for envelope env_abc123 and show me the composite hash"
• "Run AI analysis on envelope env_xyz — I want to know if there are any risky clauses before the signer reviews it"

Development

# Install dependencies
npm install

# Build
npm run build

# Run tests
npm test

# Run tests with coverage
npm run test:coverage

# Type check
npm run typecheck

# Local smoke test
SIGNATRUST_API_KEY=sk_live_xxx SIGNATRUST_API_URL=http://localhost:3000 node dist/server.js

Architecture

src/
  server.ts                      # Entry point — env validation, MCP server setup, stdio transport
  handlers.ts                    # Tool definitions and handler dispatch (testable)
  errors.ts                      # RFC 7807 ProblemDetails -> MCP tool error mapping
  vendor/signatrust-sdk/         # Vendored HTTP client + types (zero external runtime deps)
  *.test.ts                      # Co-located test files

The HTTP client and API types are vendored under src/vendor/signatrust-sdk/ so this package has no external runtime dependencies beyond @modelcontextprotocol/sdk.