Live 63 Actions

DocuSign MCP Server
for AI Agents

Q: What AI frameworks and AI clients does the StackOne DocuSign MCP server support?

The StackOne DocuSign 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.

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

Start Free Book Demo Read Docs →

DocuSign MCP Server

Built by

StackOne

Coverage

63 Agent Actions

Create, read, update, and delete across DocuSign — and extend your agent's capabilities with custom actions.

MCP Actions → Build Actions →

Authentication

Agent Tool Authentication

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

Agent Auth →

Security

Agent Protection

Every DocuSign tool response scanned for prompt injection in milliseconds — 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 DocuSign call.

Tools Discovery →

What is the DocuSign MCP Server?

A DocuSign MCP server lets AI agents read and write DocuSign data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's DocuSign MCP server ships with 63 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 DocuSign MCP Tools

Every action from DocuSign's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Brands

Create Brand
Create a new brand profile
List Brands
Get all brands in the account
Get Brand
Get a specific brand by ID
Update Brand
Update an existing brand profile
Delete Brands
Delete one or more brand profiles

Custom Fields

Add Custom Fields
Add custom fields to envelope
List Custom Fields
List envelope custom fields
Update Custom Fields
Update envelope custom fields
Delete Custom Fields
Delete envelope custom fields

Envelope Documents

List Envelope Documents
Get the list of documents in an envelope
Get Envelope Document
Download a specific document from an envelope

Documents

Add Documents
Add documents to envelope
Update Document
Replace document content with raw binary PDF
Delete Document
Remove document from envelope

Envelopes

Create Envelope
Create and send an envelope for signature
List Envelopes
List envelopes with filtering
Get Envelope
Get envelope details
Update Envelope
Send, void, or modify a draft envelope

Notification Settings

Get Notification Settings
Get envelope notification settings
Update Notification Settings
Update envelope notification settings

Envelope Locks

Create Envelope Lock
Lock an envelope
Get Envelope Lock
Get envelope lock information
Update Envelope Lock
Update envelope lock information
Delete Envelope Lock
Delete an envelope lock

Groups

Create Groups
Create one or more groups in the account
List Groups
Get groups in the account
Update Groups
Update one or more groups in the account
Delete Groups
Delete one or more groups from the account

Permission Profiles

Create Permission Profile
Create a new permission profile
List Permission Profiles
Get permission profiles in the account
Get Permission Profile
Get a specific permission profile by ID
Update Permission Profile
Update a permission profile
Delete Permission Profile
Delete a permission profile

Recipients

Create Recipient
Add recipients to envelope
List Recipients
List envelope recipients
Update Recipient
Update recipients in envelope
Delete Recipient
Remove recipient from envelope

Recipient Tabs

Create Recipient Tabs
Add tabs to a recipient
List Recipient Tabs
Get all tabs for a recipient
Update Recipient Tabs
Update tabs on a recipient
Delete Recipient Tabs
Delete tabs from a recipient

Templates

Create Template
Create a new template
List Templates
List account templates
Get Template
Get template details
Update Template
Update an existing template

Template Recipient Tabs

Create Template Recipient Tabs
Add tabs to a recipient in a template
List Template Recipient Tabs
Get all tabs for a recipient in a template
Update Template Recipient Tabs
Update tabs for a recipient in a template
Delete Template Recipient Tabs
Delete tabs from a recipient in a template

Users

Create User
Create new users in the account
List Users
Get a list of users in the account
Get User
Get a specific user by ID
Update User
Update user information
Delete Users
Close one or more users in the account

Other (9)

Get Account Information
Retrieve account details and settings
Get Form Data
Get envelope form data
List Folders
List account folders
List Template Recipients
Get template recipients
Get Recipient View URL
Get recipient view URL
Get Sender View URL
Get sender view URL
Get Edit View URL
Get edit view URL
Get Correct View URL
Get correct view URL
Move Envelopes To Recyclebin
Move envelopes to recyclebin

Set Up Your DocuSign MCP Server in Minutes

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

MCP Clients

Agent Frameworks

Claude Desktop-

JSON

Claude Desktop Docs

{
  "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 eSignature MCP Servers

69+ actions

64+ actions

60+ actions

53+ actions

All eSignature MCP Servers →

Platform Resources

MCP Code Mode: Keeping Tool Responses Out of Agent Context

Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.

11 min

Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery

Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.

10 min

Indirect Prompt Injection Defense for MCP Tools: A Technical Guide

MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.

12 min

MCP vs A2A: Architecture, Security, and When to Use Each

MCP vs A2A: what each protocol standardizes, how they differ, their shared security risks including indirect prompt injection, and when to use one, both, or a hybrid architecture.

12 min

MCP vs API: What 200+ Connector Builds Taught Us

MCP wraps APIs, it doesn't replace them. After building 200+ connectors that serve both, here's when each approach wins.

14 min read

DocuSign MCP Server FAQ

Does StackOne have a DocuSign MCP server?

Yes. StackOne offers a hosted DocuSign MCP server with 63 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.

DocuSign MCP server vs direct API integration — what's the difference?

A DocuSign MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling DocuSign. A DocuSign MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling DocuSign at runtime. StackOne provides both.

How does DocuSign authentication work for AI agents?

DocuSign authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own DocuSign account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.

Are DocuSign MCP tools vulnerable to prompt injection?

Yes — DocuSign MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — 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 — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.

What is the context bloat of a DocuSign agent and how do I avoid it?

Context bloat happens when DocuSign tool schemas and API responses eat your DocuSign agent's memory, preventing it from reasoning effectively. A single DocuSign query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.

Can I limit which actions my DocuSign agent can access?

Yes — you can limit which actions your DocuSign 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 DocuSign MCP server?

Yes — you can create custom agent actions for your DocuSign MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research DocuSign's API, generate production-ready connector YAML, test against the live API, and validate before you ship.

When should I NOT use a DocuSign MCP server?

Skip a DocuSign MCP server if your integration is purely software-to-software — direct DocuSign 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 DocuSign actions at runtime.

What AI frameworks and AI clients does the StackOne DocuSign MCP server support?

The StackOne DocuSign 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.

Start Free Book Demo

DocuSign MCP Serverfor AI Agents