SignNow API Helper MCP
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SignNow API Helper MCP How to create a signature request in Python?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SignNow API Helper MCP
An MCP server for SignNow API helper tools (stdio only).
mcp-name: io.github.signnow/sn-api-helper-mcp
Purpose & Capabilities
The SignNow API Helper MCP server is a custom Model Context Protocol server designed specifically to assist with SignNow API integration. It acts as an intelligent assistant that understands the SignNow API ecosystem to provide contextual help for developers.
Core Functions:
API Documentation Access: Retrieve and display SignNow API documentation, endpoints, and parameters.
Code Examples: Generate and provide sample code for common SignNow API operations.
Authentication Help: Assist with SignNow API authentication methods and token management.
Integration Guidance: Provide best practices for implementing SignNow e-signature workflows.
Error Resolution: Help troubleshoot common SignNow API issues and error codes.
Use Cases:
Document Signing Workflows: Help implement complex signing processes with multiple signers.
API Integration: Generate code for uploading documents, creating signature requests, and tracking status.
Development Support: Provide real-time assistance during SignNow API development.
Best Practices: Ensure proper implementation of SignNow security and compliance requirements.
Related MCP server: SignNow MCP Server
📦 Installation
To install locally for development:
pip install -e .
🚀 Run
You can run the server using Python or uvx:
Method 1: Python modulepython -m sn_api_helper_mcp serve
Method 2: Installed CLI entry pointsn-api-helper-mcp serve
Method 3: UVX uvx sn-api-helper-mcp
🔌 Integrations & Setup
You can use this server with any MCP client. Below are the configurations for the most popular IDEs and apps.
1. Claude Desktop
To use SignNow tools directly inside the Claude app:
Open your config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the following to the
mcpServersobject:
{
"mcpServers": {
"signnow-api-helper": {
"command": "uvx",
"args": [
"sn-api-helper-mcp"
]
}
}
}Restart Claude Desktop.
2. Cursor AI
Cursor supports MCP natively.
Open Cursor Settings (
Cmd/Ctrl + ,).Go to Features > MCP Servers.
Click + Add New MCP Server.
Add the following to the
mcpServersobject:
{
"mcpServers": {
"signnow-api-helper": {
"command": "uvx",
"args": ["sn-api-helper-mcp"]
}
}
}3. Visual Studio Code (via Cline)
VS Code uses the Cline extension (or similar MCP clients) to interact with MCP servers.
Install the Cline extension from the VS Code Marketplace.
Open Cline settings (click the gear icon inside the Cline chat window) -> MCP Servers.
Add the configuration JSON:
{
"signnow-api-helper": {
"command": "uvx",
"args": [
"sn-api-helper-mcp"
]
}
}✨ Features
Transport: stdio only
Available Tools:
get_signnow_api_info- Fetching API reference documentation.
Available Tools
1 toolget_signnow_api_infoB
Get information about SignNow API. This is documentation for API usage.
Inputs: query (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool clearly describes its purpose of retrieving SignNow API documentation.
The single tool follows a consistent verb_noun naming convention (get_signnow_api_info), which is clear and predictable.
With only one tool serving as documentation, the server feels extremely thin for the stated purpose. A single trivial tool is at the extreme low end of the scale.
The server provides only documentation and no actual API interaction tools, leaving significant gaps for any real SignNow workflow (e.g., document creation, signing, etc.). It is severely incomplete as an API helper.
Maintenance
Related MCP Connectors
Provides access to Avalara developer documentation, integration guides, and code examples
E-signature API: send documents for signature, track envelopes, get signed files.
Read and send documents for signature — templates, recipients, fields and folders.
Send documents for e-signature, track signing status, and download signed PDFs. No API key required.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.14MIT

SignNow MCP Serverofficial
AlicenseAqualityFmaintenancehttps://github.com/signnow/sn-mcp-server MCP server for SignNow e-signature: templates, invites, embedded signing/editor, status & downloads.258MIT- AlicenseAqualityCmaintenanceEnables sending PDFs for e-signature via the TurboSign API, with tools for sending, reviewing, tracking status, downloading signed documents, voiding, resending, and managing credentials.12MIT
- FlicenseNot gradedqualityBmaintenanceEnables access to all DocuSign product APIs through curated tools and raw API calls, with OAuth support for hosted MCP clients.-