IonBin
All pages
Search

Docusign

E-signature and agreements
OpsSalesAgreements MCPAPI/CLIFile import

Independent review. Unpaid; no partnership with Docusign. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.

E-signature platform with templates, audit trails and bulk sending on higher plans. Its MCP server brings agreement creation, sending and status tracking into supported AI tools; available actions depend on account access and administrator controls.

The Ion perspective

The five-point review

Judgment, not a score. Documentation checked 2026-10-18.

Value
E-signature platform with templates, audit trails and bulk sending on higher plans. Its MCP server brings agreement creation, sending and status tracking into supported AI tools; available actions depend on account access and administrator controls.
Differentiation
Documented fit: Teams that need e-signature with templates and audit trails; Sending envelopes and checking status from an AI assistant. Uniqueness is not established.
Replaceability and switching
Compare SignNow, PandaDoc. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Senders who exceed 5 envelopes a month on Personal or 100 per user a year on Standard and Business Pro (overages are billed). Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.

Connections: MCP connections · APIs · Portability and vendor lock-in.

Not advice

IonBin provides general information and software comparisons, not tax, legal, accounting or financial advice. Tax and legal rules vary by situation and jurisdiction; consult a qualified professional (CPA, enrolled agent or attorney) before acting.

AI tools can make mistakes. Verify every figure against the original documents and official IRS or state guidance before filing or signing.

Redact Social Security numbers, account numbers and EINs before uploading documents to any AI assistant, and check its data-retention settings. Upload originals only to the filing or signing software.

Requirements vary by state. File through official sources such as the USPTO trademark search and your state’s Secretary of State site.

Best for
  • Teams that need e-signature with templates and audit trails
  • Sending envelopes and checking status from an AI assistant
Not for
  • Senders who exceed 5 envelopes a month on Personal or 100 per user a year on Standard and Business Pro (overages are billed)

Top use cases

  • Create agreements, collect signatures and monitor status from supported AI assistants source ↗
  • Bulk send one agreement to many recipients (Business Pro) source ↗

In depth

Plans

The US checkout currently shows an annual commitment billed monthly: Personal US$11/month (US$132 commitment), Standard US$30/user/month (US$360) and Business Pro US$45/user/month (US$540). Personal includes 5 envelopes/month; Standard and Business Pro include 100 envelopes/user/year. Additional tax and envelope charges may apply. Checked 2026-10-18. source ↗

MCP access

Docusign announced general availability of its MCP server for September 30, 2026, naming Claude, ChatGPT, Gemini and other clients. The current product page describes agreement generation, signatures and status updates with account-level controls. Confirm the actions available for your Docusign plan and chosen client during setup. source ↗

How to use it with AI

How Docusign connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.

PlatformMCP / connectorAPI (agent-written code)BrowserUpload / export
Claude (incl. Claude Code) Not documented Docusign has an official MCP server and Claude (incl. Claude Code) supports MCP, but Docusign's docs don't name this pairing. Auth setup may differ. Docusign MCP docs ↗Claude (incl. Claude Code) MCP docs ↗ Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Docusign publishes an API, but this pairing still needs network, authentication and execution-scope checks. Docusign API ↗Claude (incl. Claude Code) docs ↗ Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Docusign is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Docusign's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Docusign file docs ↗Claude (incl. Claude Code) file docs ↗
OpenAI Codex Not documented Docusign has an official MCP server and OpenAI Codex supports MCP, but Docusign's docs don't name this pairing. Auth setup may differ. Docusign MCP docs ↗OpenAI Codex MCP docs ↗ Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Docusign publishes an API, but this pairing still needs network, authentication and execution-scope checks. Docusign API ↗OpenAI Codex docs ↗ Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Docusign is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Docusign's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Docusign file docs ↗OpenAI Codex file docs ↗
Google Antigravity Not documented Docusign has an official MCP server and Google Antigravity supports MCP, but Docusign's docs don't name this pairing. Auth setup may differ. Docusign MCP docs ↗Google Antigravity MCP docs ↗ Not documented Google Antigravity: Agents edit code and run tasks Docusign publishes an API, but this pairing still needs network, authentication and execution-scope checks. Docusign API ↗Google Antigravity docs ↗ Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Docusign is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Docusign's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Docusign file docs ↗Google Antigravity file docs ↗

Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.

Agent compatibility

MCPAPI/CLIFile import
LevelStatusDetail / source
Native connector / MCPYes Official docs ↗
API / CLIYes Official docs ↗
Browser / manualNo Browser access is recorded alongside a documented programmatic route.
File upload / importYes Official docs ↗

Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.

Appears in these proposed stacks

Connection capabilities to compare

An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.

Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.

Workflows using this tool

Explained in the wiki

Review

No long-form review yet. Verdict is based on research, not hands-on testing.

Alternatives

SignNow

E-signature and agreements

E-signatures with templates, signing links and an API. A hosted MCP server prepares documents, sends invites and checks status. The linked open-source repository is archived; verify maintenance before choosing a self-hosted deployment.

MCPAPI/CLIFile import
Ops

PandaDoc

E-signature and agreements

Proposals, quotes, contracts and e-signature. Its MCP server lets AI tools read, create and update documents and templates, with separate global and EU servers that only see their own region's data.

MCPAPI/CLIFile import
Sales