---
title: MCP Integration
description: Integrate Seal with AI assistants using the Model Context Protocol
---

# MCP Integration

The Seal MCP (Model Context Protocol) server enables AI assistants like Claude to interact with your Seal account directly. This allows for AI-powered document workflows, automated signing processes, and intelligent document management.

## What is MCP?

The Model Context Protocol is an open standard that allows AI assistants to securely connect to external services. Seal's MCP server provides:

- **27 Tools**: Complete API coverage for documents, recipients, templates, signatures, and uploads
- **4 Resources**: Access to documents and templates with detail views
- **OAuth 2.0**: Secure authentication with your Seal account
- **Real-time Access**: Direct integration with your organization's data

## MCP Server URL

```
https://mcp.seal.nyc
```

## Quick Start

### Claude Desktop Configuration

Add Seal to your Claude Desktop configuration:

```json
{
  "mcpServers": {
    "seal": {
      "url": "https://mcp.seal.nyc",
      "auth": {
        "type": "oauth",
        "authorizationUrl": "https://mcp.seal.nyc/.well-known/oauth-authorization-server"
      }
    }
  }
}
```

### First Use

1. **Authorize**: Claude will prompt you to authorize access to your Seal account
2. **Select Organization**: Choose which organization to connect
3. **Start Using**: Ask Claude to help with document workflows

Example prompts:

- "List my recent documents"
- "Create a new document from the Employment Contract template"
- "Show me all pending signatures"
- "Send a reminder to john@example.com for document XYZ"

## Available Tools

The MCP server provides 27 tools organized by category:

### Document Tools (8 tools)

- `seal_list_documents` - List all documents
- `seal_get_document` - Get document details
- `seal_create_document` - Create new document
- `seal_update_document` - Update document metadata
- `seal_delete_document` - Delete document
- `seal_send_document` - Send document for signing
- `seal_void_document` - Cancel document
- `seal_download_document` - Get download URL

### Recipient Tools (8 tools)

- `seal_list_recipients` - List document recipients
- `seal_get_recipient` - Get recipient details
- `seal_add_recipient` - Add recipient to document
- `seal_update_recipient` - Update recipient info
- `seal_remove_recipient` - Remove recipient
- `seal_send_reminder` - Send signing reminder
- `seal_add_recipients_bulk` - Add multiple recipients at once
- `seal_update_recipients_bulk` - Update multiple recipients at once

### Template Tools (7 tools)

- `seal_list_templates` - List all templates
- `seal_get_template` - Get template details
- `seal_get_template_fields` - Get template field definitions
- `seal_create_template` - Create template from document
- `seal_update_template` - Update template metadata
- `seal_delete_template` - Delete template
- `seal_use_template` - Create document from template

### Signature Tools (4 tools)

- `seal_list_signatures` - List document signatures
- `seal_get_signature` - Get signature details
- `seal_verify_document` - Verify document signatures
- `seal_get_audit_trail` - Get complete audit trail

### Upload Tools (2 tools)

- `seal_upload_file` - Upload a PDF file from local path (stdio mode only)
- `seal_upload_file_content` - Upload a PDF using base64-encoded content (all modes)

## Available Resources

Resources provide read-only access to your Seal data:

- `seal://documents` - Browse all documents
- `seal://documents/{id}` - Get detailed document information
- `seal://templates` - Browse all templates
- `seal://templates/{id}` - Get detailed template with field definitions

## Authentication

The MCP server uses OAuth 2.0 via Seal's own authorization server (Better-Auth) for secure authentication:

1. **OAuth Flow**: Standard OAuth 2.0 authorization code flow
2. **Scopes**: Full API access (all seal:\* scopes)
3. **Token Storage**: Tokens are stored securely by the MCP client
4. **Refresh**: Tokens are automatically refreshed when expired

### OAuth Endpoints

- **Authorization Server**: `https://mcp.seal.nyc/.well-known/oauth-authorization-server`
- **Protected Resource**: `https://mcp.seal.nyc/.well-known/oauth-protected-resource/mcp`

## Use Cases

### Automated Document Workflows

```
User: "Create a new employment contract for John Doe (john@example.com)
       using the Employment Contract template, with a start date of Feb 1st
       and salary of $75,000"

Claude: I'll create that document for you using the template.
        [Uses seal_use_template and seal_send_document tools]
        ✓ Document created: "John Doe Employment Contract"
        ✓ Sent to john@example.com for signing
```

### Document Status Tracking

```
User: "Show me all documents waiting for signatures"

Claude: [Uses seal_list_documents with status filter]
        You have 3 documents pending signatures:
        1. Service Agreement - 1/2 signed
        2. NDA - 0/1 signed
        3. Contract Amendment - 2/3 signed
```

### Bulk Operations

```
User: "Send reminders to all recipients who haven't signed in the last 3 days"

Claude: [Uses seal_list_documents and seal_send_reminder tools]
        Sent reminders to 5 recipients across 3 documents.
```

## Security & Privacy

- **OAuth Authentication**: Industry-standard secure authentication
- **Organization Scoped**: Access limited to your selected organization
- **Audit Trail**: All MCP actions are logged in document audit trails
- **Revocable**: Disconnect MCP access anytime from your Seal account (Settings → Developer) or your MCP client

> **Info**
>
> **Privacy**: The MCP server only accesses data you explicitly authorize. AI
> assistants cannot access your Seal account without your permission.

## Limitations

- **Rate Limits**: Same rate limits as REST API (60/min, 1000/hour)
- **File Uploads**: Large file uploads may be slower through MCP
- **Real-time Updates**: Use webhooks for real-time notifications

## Next Steps

- **[MCP Tools Reference](/docs/mcp/tools)** - Complete tool documentation
- **[MCP Authentication](/docs/mcp/authentication)** - OAuth setup guide
- **[API Reference](/docs/api-reference)** - Underlying REST API documentation