Skip to main content Announcing Tool Policies: AI agent permissions down to the field Read the announcement
Live 29 Actions

SignNow MCP Server
for AI Agents

Connect your AI agent to StackOne's SignNow MCP server and give it 29 MCP tools out of the box. Auth, tool execution, and security all managed.

SignNow logo
SignNow MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

29 Agent Actions

Agents can read, write, delete and run operations in SignNow. Extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your SignNow MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every SignNow tool response scanned for prompt injection in milliseconds, with 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every SignNow call.

Tools Discovery →

What is the SignNow MCP Server?

A SignNow MCP server lets AI agents read and write SignNow data through the Model Context Protocol, Anthropic's open standard for connecting LLMs to external tools. StackOne's SignNow MCP server ships with 29 pre-built actions, fully extensible via the Connector Builder, plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All SignNow MCP Tools

Every StackOne action for SignNow, ready for your agent. Read, write, delete and run operations, scoped to exactly what you need.

Documents

  • Upload Document

    Upload a new document file to SignNow.

  • Get Document

    Retrieve a document's full details by id.

  • Download Document

    Download a document as a PDF or ZIP file.

  • Delete Document

    Permanently delete a document.

Merge Documents

  • Merge Documents

    Merge multiple documents into a single document.

Document Historys

  • Get Document History

    Retrieve the full audit history of a document.

Invite To Signs

  • Invite To Sign

    Send a document that already has signature fields out for signature, approval or viewing.

Cancel Invites

  • Cancel Invite

    Cancel the pending signing invite on a document that has not yet completed.

Document Groups

  • Create Document Group

    Group multiple documents together for a single signing flow.

  • Get Document Group

    Retrieve a document group's details by id.

  • List Document Groups

    List the caller's document groups with pagination.

  • Delete Document Group

    Remove a document group while keeping its documents intact.

Invite To Sign Document Groups

  • Invite To Sign Document Group

    Send a document group out for signature as one coordinated, multi-step flow.

Event Subscriptions

  • Create Event Subscription

    Create a webhook event subscription that calls a callback URL when an event fires.

  • List Event Subscriptions

    List configured webhook event subscriptions.

  • Update Event Subscription

    Update the event, entity and delivery config of an existing webhook subscription.

  • Delete Event Subscription

    Delete a webhook event subscription so its callback stops receiving events.

Folders

  • Create Folder

    Create a new folder for organizing documents under an existing parent.

  • List Folders

    List the caller's top-level system folders and their ids.

  • Get Folder

    Retrieve a specific folder's contents (documents, templates, groups) by id.

  • Delete Folder

    Permanently remove a folder from the caller's account.

Templates

  • Create Template

    Convert an existing document into a reusable template.

  • List Templates

    List templates stored in a folder.

  • Get Template

    Retrieve a template's full details by id.

Document From Templates

  • Create Document From Template

    Create a new document by copying a template.

Duplicate Templates

  • Duplicate Template

    Duplicate a template as a new, independent template.

Template Routing Details

  • Get Template Routing Details

    Retrieve a template's signer and approver routing configuration.

Users

  • Create User

    Create a new SignNow user account (requires an elevated organization-management token).

User Infos

  • Get User Info

    Retrieve the authenticated user's profile, subscription and organization details.

Set Up Your SignNow MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to SignNow in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More Documents & Knowledge MCP Servers

Nextcloud

431+ actions

Workiva

266+ actions

WordPress

178+ actions

Confluence

145+ actions

Lokalise

111+ actions

NinjaOne

105+ actions

Envi

104+ actions

SignNow MCP Server FAQ

Does StackOne have a SignNow MCP server?
Yes. StackOne offers a hosted SignNow MCP server with 29 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
SignNow MCP server vs direct API integration: what's the difference?
A SignNow MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software work, where backend code calls SignNow. A SignNow MCP server is for AI agents that discover and call SignNow at runtime, such as MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI. StackOne provides both.
How does SignNow authentication work for AI agents?
SignNow authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK to get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own SignNow account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are SignNow MCP tools vulnerable to prompt injection?
Yes. SignNow MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content, such as documents, messages, tickets, records, or free-text fields, is a potential vector. StackOne Defender scans every tool response before it enters the agent's context. It runs regex patterns in ~1ms, then a MiniLM classifier in ~4ms. Accuracy is 88.7%, and it runs entirely on CPU.
What is the context bloat of a SignNow agent and how do I avoid it?
Context bloat happens when SignNow tool schemas and API responses eat your SignNow agent's memory, preventing it from reasoning effectively. A single SignNow query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery reduces it by loading only the tools relevant to each query.
Can I limit which actions my SignNow agent can access?
Yes. You can limit which actions your SignNow agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my SignNow MCP server?
Yes. You can create custom agent actions for your SignNow MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research SignNow's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a SignNow MCP server?
Skip a SignNow MCP server if your integration is purely software-to-software, because direct SignNow API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call SignNow actions at runtime.
What AI frameworks and AI clients does the StackOne SignNow MCP server support?
The StackOne SignNow MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.