developer-tools

SignNow MCP Server

signnow

by signnow

SignNow MCP Server — document signing server for SignNow API. Manage templates, invites, embedded signing, status and do

https://github.com/signnow/sn-mcp-server MCP server for SignNow e-signature: templates, invites, embedded signing/editor, status & downloads.

github stars

5

0 commentsdiscussion

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

Real-time signature status trackingRole-based multi-signer supportEmbedded workflow capabilities

best for

  • / Developers building e-signature into applications
  • / Automating contract and document approval workflows
  • / Creating branded embedded signing experiences

capabilities

  • / Send documents for signature with role-based signing order
  • / Create and manage reusable document templates
  • / Track signature progress in real-time
  • / Download completed signed documents
  • / Embed signing and editing workflows
  • / Pre-fill document fields with data

what it does

Connects AI agents to SignNow's e-signature platform for sending documents, managing templates, tracking signature status, and handling embedded signing workflows.

about

SignNow MCP Server is an official MCP server published by signnow that provides AI assistants with tools and capabilities via the Model Context Protocol. SignNow MCP Server — document signing server for SignNow API. Manage templates, invites, embedded signing, status and do It is categorized under developer tools.

how to install

You can install SignNow 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

SignNow 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

About SignNow API

The SignNow REST API empowers users to deliver a seamless eSignature experience for signers, preparers, and senders. Pre-fill documents, create embedded branded workflows for multiple signers, request payments, and track signature status in real-time. Ensure signing is simple, secure, and intuitive on any device. **What you can do with the SignNow API**: * Send documents and document groups for signature in a role-based order * Create reusable templates from documents * Pre-fill document fields with data * Collect payments as part of the signing flow * Embed the document sending, signing, or editing experience into your website, application, or any system of record * Track signing progress and download the completed documents
--- # SignNow MCP Server > A Model Context Protocol (MCP) server that gives AI agents secure, structured access to **SignNow** eSignature workflows — templates, embedded signing, invites, status tracking, and document downloads — over **STDIO** or **Streamable HTTP**. > mcp-name: io.github.signnow/sn-mcp-server --- ## Table of contents * [Features](#features) * [Quick start](#quick-start) * [Prerequisites](#prerequisites) * [Quick run (uvx)](#quick-run-uvx) * [1. Setup Environment Variables](#1-setup-environment-variables) * [2. Install and Run](#2-install-and-run) * [Local/Remote (HTTP)](#localremote-http) * [Docker](#docker) * [Docker Compose](#docker-compose) * [Configuration](#configuration) * [Authentication options](#authentication-options) * [SignNow & OAuth settings](#signnow--oauth-settings) * [Production key management](#production-key-management) * [Client setup](#client-setup) * [VS Code — GitHub Copilot (Agent Mode) / Cursor](#vs-code--github-copilot-agent-mode--cursor) * [Claude Desktop](#claude-desktop) * [Glama (hosted MCP)](#glama-hosted-mcp) * [MCP Inspector (testing)](#mcp-inspector-testing) * [Tools](#tools) * [FAQ / tips](#faq--tips) * [Examples](#examples) * [Useful resources](#useful-resources) * [Sample apps](#sample-apps) * [API documentation](#api-documentation) * [SignNow API Helper MCP](#signnow-api-helper-mcp) * [License](#license) --- ## Features * **Templates & groups** * Browse all templates and template groups * Create documents or groups from templates (one-shot flows included) * **Invites & embedded UX** * Email invites and ordered recipients * **Embedded signing/sending/editor** links for in-app experiences * **Status & retrieval** * Check invite status and step details * Download final documents (single or merged) * Read normalized document/group structure for programmatic decisions * **Transports** * **STDIO** (best for local clients) * **Streamable HTTP** (best for Docker/remote) --- ## Quick start ### Prerequisites - SignNow account. Create a [free developer account](https://www.signnow.com/developers). - SignNow Credentials: You will need your account email, password, and the application Basic Authorization Token. [Getting started](https://docs.signnow.com/docs/signnow/get-started). - An active SignNow API application. - Python 3.11+ installed on your system (check with python3 --version) - UVX installed  (check with uvx --version). Recommended for the quickest setup. - Environment variables configured - If your client supports Streamable HTTP, you can use the pre-deployed server URL `https://mcp-server.signnow.com/mcp` instead of running it locally. ### Quick run (uvx) If you use `uv`, you can run the server without installing the package: ```bash uvx --from signnow-mcp-server sn-mcp serve ``` ### 1. Setup Environment Variables ```bash # Create .env file with your SignNow credentials # You can copy from env.example if you have the source code # Or create .env file manually with required variables (see Environment Variables section below) ``` ### 2. Install and Run #### Option A: Install from PyPI (Recommended) ```bash # Install the package from PyPI pip install signnow-mcp-server # Run MCP server in standalone mode sn-mcp serve ``` #### Option B: Install from Source (Development) ```bash # 1) Clone & configure git clone https://github.com/signnow/sn-mcp-server.git cd sn-mcp-server cp .env.example .env # fill in your values in .env # 2) Install (editable for dev) pip install -e . # 3) Run as STDIO MCP server (recommended for local tools & Inspector) sn-mcp serve ``` > STDIO is ideal for desktop clients and local testing. ### Local/Remote (HTTP) ```bash # Start HTTP server on 127.0.0.1:8000 sn-mcp http # Custom host/port sn-mcp http --host 0.0.0.0 --port 8000 # Dev reload sn-mcp http --reload ``` By default, the **Streamable HTTP** MCP endpoint is served under `/mcp`. Example URL: ``` http://localhost:8000/mcp ``` ### Docker ```bash # Build docker build -t sn-mcp-server . # Run HTTP mode (recommended for containers) docker run --env-file .env -p 8000:8000 sn-mcp-server sn-mcp http --host 0.0.0.0 --port 8000 ``` > STDIO inside containers is unreliable with many clients. Prefer HTTP when using Docker. ### Docker Compose ```bash # Only the MCP server docker-compose up sn-mcp-server # Both services (if defined) docker-compose up ``` --- ## Configuration Copy `.env.example` → `.env` and fill in values. All settings are validated via **pydantic-settings** at startup. ### Authentication options **1) Username / Password (recommended for desktop dev flows)** ``` SIGNNOW_USER_EMAIL= SIGNNOW_PASSWORD= SIGNNOW_API_BASIC_TOKEN= ``` **2) OAuth 2.0 (for hosted/advanced scenarios)** ``` SIGNNOW_CLIENT_ID= SIGNNOW_CLIENT_SECRET= # + OAuth server & RSA settings below ``` > When running via some desktop clients, only user/password may be supported. ### SignNow & OAuth settings ``` # SignNow endpoints (defaults shown) SIGNNOW_APP_BASE=https://app.signnow.com SIGNNOW_API_BASE=https://api.signnow.com # Optional direct API token (not required for normal use) SIGNNOW_TOKEN= # OAuth server (if you enable OAuth mode) OAUTH_ISSUER= ACCESS_TTL=3600 REFRESH_TTL=2592000 ALLOWED_REDIRECTS= # RSA keys for OAuth (critical in production) OAUTH_RSA_PRIVATE_PEM= OAUTH_JWK_KID= ``` ### Production key management If `OAUTH_RSA_PRIVATE_PEM` is missing in production, a new RSA key will be generated on each restart, **invalidating all existing tokens**. Always provide a persistent private key via secrets management in prod. --- ## Client setup ### VS Code — GitHub Copilot (Agent Mode) / Cursor Create `.vscode/mcp.json` / `.cursor/mcp.json` in your workspace: **STDIO (local):** ```json { "servers": { "signnow": { "command": "sn-mcp", "args": ["serve"], "env": { "SIGNNOW_USER_EMAIL": "${env:SIGNNOW_USER_EMAIL}", "SIGNNOW_PASSWORD": "${env:SIGNNOW_PASSWORD}", "SIGNNOW_API_BASIC_TOKEN": "${env:SIGNNOW_API_BASIC_TOKEN}" } } } } ``` **STDIO (uvx — no local install):** ```json { "servers": { "signnow": { "command": "uvx", "args": ["--from", "signnow-mcp-server", "sn-mcp", "serve"], "env": { "SIGNNOW_USER_EMAIL": "${env:SIGNNOW_USER_EMAIL}", "SIGNNOW_PASSWORD": "${env:SIGNNOW_PASSWORD}", "SIGNNOW_API_BASIC_TOKEN": "${env:SIGNNOW_API_BASIC_TOKEN}" } } } } ``` **HTTP (remote or Docker):** ```json { "servers": { "signnow": { "type": "http", "url": "http://localhost:8000/mcp" } } } ``` Then open Chat → **Agent mode**, enable the **signnow** tools, and use them in prompts. Note: The same configuration applies in Cursor — add it under MCP settings (STDIO or HTTP). For STDIO, you can also use `uvx` as shown above. ### Claude Desktop Use Desktop Extensions or the manual MCP config (Developer → Edit config). Steps: 1. Open Claude Desktop → Developer → Edit config 2. Add a new server entry under `mcpServers` 3. Save and restart Claude Desktop Examples: **STDIO (local install):** ```json { "mcpServers": { "signnow": { "command": "sn-mcp", "args": ["serve"], "env": { "SIGNNOW_USER_EMAIL": "${env:SIGNNOW_USER_EMAIL}", "SIGNNOW_PASSWORD": "${env:SIGNNOW_PASSWORD}", "SIGNNOW_API_BASIC_TOKEN": "${env:SIGNNOW_API_BASIC_TOKEN}" } } } } ``` **STDIO (uvx — no local install):** ```json { "mcpServers": { "signnow": { "command": "uvx", "args": ["--from", "signnow-mcp-server", "sn-mcp", "serve"], "env": { "SIGNNOW_USER_EMAIL": "${env:SIGNNOW_USER_EMAIL}", "SIGNNOW_PASSWORD": "${env:SIGNNOW_PASSWORD}", "SIGNNOW_API_BASIC_TOKEN": "${env:SIGNNOW_API_BASIC_TOKEN}" } } } } ``` **HTTP (remote or Docker):** ```json { "mcpServers": { "signnow": { "type": "http", "url": "http://localhost:8000/mcp" } } } ``` Then enable the server in Claude’s chat and start using the tools. ### Glama (hosted MCP) Deploy and run this server on Glama with minimal setup: Steps: 1. Open the server page on Glama: [sn-mcp-server on Glama](https://glama.ai/mcp/servers/@mihasicehcek/sn-mcp-server) 2. Click the red "Deploy Server" button 3. In environment variables, provide: - `SIGNNOW_USER_EMAIL` - `SIGNNOW_PASSWORD` - `SIGNNOW_API_BASIC_TOKEN` - (other variables can be left as defaults) 4. Create an access token in Glama and copy the endpoint URL. It will look like: ``` https://glama.ai/endpoints/{someId}/mcp?token={glama-mcp-token} ``` Use this HTTP MCP URL in any client that supports HTTP transport (e.g., VS Code/Cursor JSON config or Claude Desktop HTTP example above). ### MCP Inspector (testing) Great for exploring tools & schemas visually. ```bash # Start Inspector (opens UI on localhost) npx @modelcontextprotocol/inspector # Connect (STDIO): run your server locally and attach sn-mcp serve # Or connect ---

FAQ

What is the SignNow MCP Server MCP server?
SignNow 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 SignNow MCP Server?
This profile displays 28 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.528 reviews
  • Shikha Mishra· Dec 16, 2024

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

  • Ama Smith· Dec 12, 2024

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

  • Yash Thakker· Nov 7, 2024

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

  • Emma Ghosh· Nov 3, 2024

    I recommend SignNow MCP Server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Dhruvi Jain· Oct 26, 2024

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

  • Ishan Harris· Oct 22, 2024

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

  • Alexander Liu· Sep 25, 2024

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

  • Alexander Farah· Sep 5, 2024

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

  • Kwame Anderson· Sep 1, 2024

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

  • Aditi Brown· Aug 24, 2024

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

showing 1-10 of 28

1 / 3