
SignNow Api Helper MCP
io.github.signnowPublished by GitHub account signnowv0.1.1Updated Oct 24, 2026
MCP server for SignNow API helper tools (stdio only).
Overview
A local stdio MCP server that gives an assistant SignNow API reference documentation and integration guidance for e-signature development.
- What you can do
- Fetch SignNow API reference documentation, endpoints and parameters
- Provide sample code for common SignNow API operations
- Explain authentication methods and token management
- Offer best practices for e-signature workflows and troubleshooting of error codes
- When to use it
- Useful when building or debugging a SignNow e-signature integration and you want the assistant to look up API details and produce example code in the same conversation.
- Requirements
- Runs locally over stdio as a Python package (sn-api-helper-mcp), launched via uvx, the CLI entry point, or python -m sn_api_helper_mcp serve. No environment variables, headers or credentials are declared; it is desktop-only.
Installation
In SourceWeft
- Open SignNow Api Helper MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
📦 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.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Add the following to the
mcpServersobject:
- 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:
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:
✨ Features
- Transport: stdio only
- Available Tools:
get_signnow_api_info- Fetching API reference documentation.
Source: README.md at commit 8e3ae5a
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts