Skip to main content
Glama
signnow

SignNow API Helper MCP

Official
by signnow
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

SignNow API Helper MCP

PyPI License

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:

  1. Open your config file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

  2. Add the following to the mcpServers object:

{
  "mcpServers": {
    "signnow-api-helper": {
      "command": "uvx",
      "args": [
        "sn-api-helper-mcp"
      ]
    }
  }
}

  1. Restart Claude Desktop.

2. Cursor AI

Cursor supports MCP natively.

  1. Open Cursor Settings (Cmd/Ctrl + ,).

  2. Go to Features > MCP Servers.

  3. Click + Add New MCP Server.

  4. Add the following to the mcpServers object:

{
  "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.

  1. Install the Cline extension from the VS Code Marketplace.

  2. Open Cline settings (click the gear icon inside the Cline chat window) -> MCP Servers.

  3. 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 tool
get_signnow_api_infoB

Get information about SignNow API. This is documentation for API usage.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesQuery string to search for API information (e.g., 'free form invite')

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates the tool is for looking up documentation (implying read-only), but it does not describe return format, pagination, rate limits, or any other behavioral traits. The description is too thin to be transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences, front-loaded with the primary action and resource. Every sentence contributes meaningful context, with no redundancy or filler. It is appropriately concise for a simple lookup tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter) and the presence of an output schema, the description need not explain return values. However, it lacks any detail about what kind of API information can be queried or how the documentation is structured. It is minimally complete but leaves room for clarification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the 'query' parameter already described as 'Query string to search for API information'. The description adds no additional parameter semantics, but with full schema coverage, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and resource ('SignNow API'), and clarifies that it provides API usage documentation. It effectively communicates the tool's scope, though it is somewhat broad ('information' could be more specific). No sibling tools exist, so differentiation isn't applicable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving API documentation via a query string, but does not provide explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. The context is clear but only implied from 'documentation for API usage'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedget_signnow_api_info
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The tool clearly describes its purpose of retrieving SignNow API documentation.

Naming Consistency5/5

The single tool follows a consistent verb_noun naming convention (get_signnow_api_info), which is clear and predictable.

Tool Count1/5

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.

Completeness1/5

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

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • BoldSign MCP Server

    Synctest-hub
    A
    license
    A
    quality
    D
    maintenance
    Enables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.
    14
    32
    MIT

  • Aoexl Sign

    aryansingh0203
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables users to create, manage, and track electronic signing requests and templates through Claude Desktop and other MCP-compatible clients. Provides multi-tenant authentication with customer API keys for secure document workflow operations.
    66
    -
  • SignaTrust MCP Server by SignaTrustDev

    SignaTrust MCP Serverofficial

    SignaTrustDev
    A
    license
    A
    quality
    C
    maintenance
    Enables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.
    8
    50
    1
    MIT