developer-tools

SendForSign MCP Server

sendforsign

by sendforsign

SendForSign MCP Server: use the SendForSign API to list e-signature templates and read template content for streamlined

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

github stars

0

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Direct SendForSign API accessTemplate management focused

best for

  • / Developers building e-signature integrations
  • / Automating document signature workflows
  • / Managing electronic signature templates

capabilities

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

what it does

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

about

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

MIT

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.

readme

Sendforsign MCP Server

A Model Context Protocol (MCP) server implementation that integrates with [Sendforsign](https://sendforsign.com) 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 ```bash env SFS_API_KEY=YOUR_API_KEY SFS_CLIENT_KEY=YOUR_CLIENT_KEY npx -y @sendforsign/mcp ``` ### Manual Installation ```bash 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](https://docs.cursor.com/context/model-context-protocol#configuring-mcp-servers) 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: ```json { "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`: ```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: ```bash # 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`: ```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:** ```json { "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:** ```json { "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 ```bash 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 ```bash # 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 ```bash curl -sS http://localhost:3000/health ``` ## Development ```bash # Install dependencies npm install # Build npm run build # Run development server npm run dev ``` ## License MIT License - see LICENSE file for details

FAQ

What is the SendForSign MCP Server MCP server?
SendForSign MCP Server is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for SendForSign MCP Server?
This profile displays 25 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.525 reviews
  • Chaitanya Patil· Dec 28, 2024

    Strong directory entry: SendForSign MCP Server surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Evelyn Khan· Dec 24, 2024

    We wired SendForSign MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Pratham Ware· Dec 8, 2024

    According to our notes, SendForSign MCP Server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Isabella Gonzalez· Dec 8, 2024

    SendForSign MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Nikhil Gupta· Nov 27, 2024

    Useful MCP listing: SendForSign MCP Server is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Piyush G· Nov 19, 2024

    SendForSign MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Yuki Zhang· Nov 15, 2024

    SendForSign MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Nia Desai· Oct 18, 2024

    SendForSign MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Shikha Mishra· Oct 10, 2024

    We evaluated SendForSign MCP Server against two servers with overlapping tools; this profile had the clearer scope statement.

  • Yuki Diallo· Oct 6, 2024

    Useful MCP listing: SendForSign MCP Server is the kind of server we cite when onboarding engineers to host + tool permissions.

showing 1-10 of 25

1 / 3