SendForSign MCP Server

SendForSign MCP Server

Official
sendforsign

Connects to SendForSign's electronic signature service to retrieve and manage document templates for signature workflows.

Enables interaction with the SendForSign API to list document templates and read template content for electronic signature workflows.

126 views2Local (stdio)

What it does

  • List available document templates
  • Read template content and metadata
  • Access SendForSign API endpoints
  • Retrieve template configurations

Best for

Developers building e-signature integrationsAutomating document signature workflowsManaging electronic signature templates
Direct SendForSign API accessTemplate management focused

About SendForSign MCP Server

SendForSign MCP Server is an official MCP server published by sendforsign that provides AI assistants with tools and capabilities via the Model Context Protocol. SendForSign MCP Server: use the SendForSign API to list e-signature templates and read template content for streamlined It is categorized under developer tools.

How to install

You can install SendForSign MCP Server in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

SendForSign MCP Server is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

Sendforsign MCP Server

A Model Context Protocol (MCP) server implementation that integrates with Sendforsign for document template management and signing workflows.

Features

  • Template listing and content reading
  • Flexible authentication (API keys via env vars or HTTP headers)
  • Dual transport support (stdio for MCP clients, HTTP Stream for web APIs)
  • Docker ready deployment
  • Health monitoring

Installation

Running with npx

env SFS_API_KEY=YOUR_API_KEY SFS_CLIENT_KEY=YOUR_CLIENT_KEY npx -y @sendforsign/mcp

Manual Installation

npm install -g @sendforsign/mcp

Running on Cursor

For the most up-to-date configuration instructions, please refer to the official Cursor documentation on configuring MCP servers: Cursor MCP Server Configuration Guide

To configure SendForSign MCP in Cursor:

  1. Open Cursor Settings
  2. Go to Features > MCP Servers
  3. Click "+ Add new global MCP server"
  4. Enter the following code:
    {
      "mcpServers": {
        "sendforsign-mcp": {
          "command": "npx",
          "args": ["-y", "@sendforsign/mcp"],
          "env": {
            "SFS_API_KEY": "YOUR-API-KEY",
            "SFS_CLIENT_KEY": "YOUR-CLIENT-KEY"
          }
        }
      }
    }
    

Running on Windsurf

Add this to your ./codeium/windsurf/model_config.json:

{
  "mcpServers": {
    "sendforsign-mcp": {
      "command": "npx",
      "args": ["-y", "@sendforsign/mcp"],
      "env": {
        "SFS_API_KEY": "YOUR_API_KEY",
        "SFS_CLIENT_KEY": "YOUR_CLIENT_KEY"
      }
    }
  }
}

Running with HTTP Stream Mode

To run the server using HTTP Stream locally instead of the default stdio transport:

# Option 1: Using HTTP_STREAMABLE_SERVER
env HTTP_STREAMABLE_SERVER=true SFS_API_KEY=YOUR_API_KEY SFS_CLIENT_KEY=YOUR_CLIENT_KEY npx -y @sendforsign/mcp

# Option 2: Using CLOUD_SERVICE
env CLOUD_SERVICE=true SFS_API_KEY=YOUR_API_KEY SFS_CLIENT_KEY=YOUR_CLIENT_KEY npx -y @sendforsign/mcp

Use the url: http://localhost:3000/mcp

Configuration

Environment Variables

Required

  • SFS_API_KEY: Your SendForSign API key
  • SFS_CLIENT_KEY: Your SendForSign client key

Optional

  • HTTP_STREAMABLE_SERVER: Set to true to enable HTTP Stream transport
  • CLOUD_SERVICE: Set to true to enable HTTP Stream transport (alternative to HTTP_STREAMABLE_SERVER)
  • SSE_LOCAL: Set to true to enable HTTP Stream transport (alternative to HTTP_STREAMABLE_SERVER)
  • PORT: Server port (default: 3000)
  • HOST: Server host (default: localhost)

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "sendforsign-mcp": {
      "command": "npx",
      "args": ["-y", "@sendforsign/mcp"],
      "env": {
        "SFS_API_KEY": "YOUR_API_KEY_HERE",
        "SFS_CLIENT_KEY": "YOUR_CLIENT_KEY_HERE"
      }
    }
  }
}

Available Tools

1. List Templates (sfs_list_templates)

List all SendForSign templates for the authenticated client.

Best for:

  • Discovering available templates
  • Getting template metadata

Usage Example:

{
  "name": "sfs_list_templates",
  "arguments": {}
}

Returns: Array of templates with their keys and metadata.

2. Read Template (sfs_read_template)

Read the content of a specific SendForSign template.

Best for:

  • Getting template content for editing or analysis
  • Template inspection

Usage Example:

{
  "name": "sfs_read_template",
  "arguments": {
    "templateKey": "your-template-key"
  }
}

Returns: Template content and metadata.

HTTP Stream API

When running in HTTP Stream mode, the server provides REST endpoints:

  • GET /health - Health check
  • POST /mcp - MCP protocol endpoint

Authentication via HTTP Headers

Send API keys in HTTP headers:

API Key (choose one):

  • X-Sendforsign-Key: YOUR-API-KEY
  • X-Api-Key: YOUR-API-KEY

Client Key:

  • X-Client-Key: YOUR-CLIENT-KEY

Example API Call

curl -X POST http://localhost:3000/mcp \
  -H "Content-Type: application/json" \
  -H "X-Sendforsign-Key: YOUR-API-KEY" \
  -H "X-Client-Key: YOUR-CLIENT-KEY" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {}}'

Docker Deployment

Build and Run

# Build image
docker build -t sendforsign/mcp:latest .

# Run container
docker run --rm -p 3000:3000 \
  -e CLOUD_SERVICE=true \
  -e SFS_API_KEY=YOUR-API-KEY \
  -e SFS_CLIENT_KEY=YOUR-CLIENT-KEY \
  sendforsign/mcp:latest

Health Check

curl -sS http://localhost:3000/health

Development

# Install dependencies
npm install

# Build
npm run build

# Run development server
npm run dev

License

MIT License - see LICENSE file for details

Alternatives

Related Skills

Browse all skills
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

18
ai-sdk

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

6
api-documenter

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

4
openai-knowledge

Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.

4
cli-builder

Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.

3
ydc-ai-sdk-integration

Integrate Vercel AI SDK applications with You.com tools (web search, AI agent, content extraction). Use when developer mentions AI SDK, Vercel AI SDK, generateText, streamText, or You.com integration with AI SDK.

2