📅 Book a 30-min Demo📞 Call/text (571) 293-0242
Connector · Electronic signature platform

Docusign eSignature MCP Server & Agent Skill

Last updated

ibl.ai publishes a free Docusign eSignature agent skill: a SKILL.md that teaches an AI agent to read and write Docusign eSignature data and expose it as an MCP tool. Download it, connect your own Docusign eSignature credentials, and run the agent on ibl.ai Agentic OS, where you own all the code and the data.

Docusign eSignature sends documents for electronic signature and tracks them. Accounts hold envelopes (documents, recipients, tabs and status), templates, signed documents and certificates of completion.

What is the Docusign eSignature API, and what can an agent read from it?

REST endpoints under /restapi/v2.1/accounts/{accountId}/ for envelopes (create, send, status), envelope documents and recipients, and templates. Free developer accounts run against the demo environment.

  • API: Docusign eSignature REST API (v2.1) (REST)
  • Access: Public, self-serve
  • Base URL: {base_uri}/restapi/v2.1/accounts/{accountId}/ where base_uri comes from the OAuth userinfo call (demo accounts use demo.docusign.net)
  • Authentication: OAuth 2.0 authorization code; OAuth 2.0 JWT grant

Anyone can open a free Docusign developer account and create an integration key under Apps and Keys. Moving an app to production accounts requires Docusign's go-live review.

Auth servers: account-d.docusign.com (demo) and account.docusign.com (production). JWT grant uses an integration key, RSA key pair and impersonated user ID with scopes signature and impersonation; base_uri comes from userinfo.

What can an agent read from Docusign eSignature?

  • Envelopes — GET /v2.1/accounts/{accountId}/envelopes and /envelopes/{envelopeId} for status and details.
  • Envelope documents — GET /envelopes/{envelopeId}/documents/{documentId} to download a signed or unsigned document.
  • Recipients — GET /envelopes/{envelopeId}/recipients for signer status.
  • Templates — GET /v2.1/accounts/{accountId}/templates.

What can an agent write to Docusign eSignature?

  • Envelopes (send) — POST /v2.1/accounts/{accountId}/envelopes creates a draft or sends documents to signers. Confirm with the user first.
  • Envelope updates — PUT /envelopes/{envelopeId} to send or modify a draft, void an in-process envelope, or purge documents. Confirm with the user first.
  • Recipients — Add, update or delete recipients on an envelope. Confirm with the user first.
  • Templates — POST or PUT /v2.1/accounts/{accountId}/templates.

Limits: Each account has an hourly request limit shown in X-RateLimit-Limit, reset on the hour. GET/PUT per envelope per hour is limited, and apps may poll status at most once per envelope per 15 minutes; use Connect webhooks.

Envelopes often carry privileged or confidential agreements, and financial or personal data; sending is an outward, legally binding act that needs human approval.

How do I connect Docusign eSignature to an AI agent over MCP?

Docusign publishes an official MCP server: Docusign MCP Server.

Docusign-hosted at https://mcp.docusign.com/mcp (demo: https://mcp-d.docusign.com/mcp). Tools send envelopes, check status and manage templates; official connectors for Claude, ChatGPT and others.

You can register that server on ibl.ai as it is, or use the SKILL.md below when you want the agent to call the Docusign eSignature REST API (v2.1) directly.

On ibl.ai an MCP connection is three records, and a working integration always needs all three:

  1. Register the server — POST …/mcp-servers/ with its URL, a transport (sse, websocket or streamable_http) and an auth_type of none, token or oauth2.
  2. Create a connection that holds the credential, scoped to the whole organization (platform), to a single agent, or to each user (user).
  3. Enable it on the agent — mcp-tool in tool_slugs and the server id in mcp_servers. Both lists are replaced, not merged, so read the settings first.

Docusign eSignature supports per-user OAuth, so the server can use auth_type=oauth2 with auth_scope=user: each person connects their own Docusign eSignature account in the chat the first time the agent needs it.

The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.

What does the Docusign eSignature agent skill do?

The Docusign eSignature skill is one SKILL.md file named iblai-connect-docusign. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.

Download the Docusign eSignature SKILL.md

Save it as .claude/skills/iblai-connect-docusign/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:

$ npx skills add iblai/vibe --all

This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.

It was checked against Docusign's documentation on October 20, 2026. Test it against your own Docusign eSignature setup before you rely on it.

What can I ask a Docusign eSignature agent to do?

  • “Which envelopes sent this week are still waiting on a signature?”
  • “Send the NDA template to jane@acme.com for signature”
  • “Download the completed engagement letter for envelope 3f2a...”
  • “Remind the remaining signers on the Beta Corp MSA”

How do I run a Docusign eSignature agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the Docusign eSignature MCP connection, the model the agent uses, its instructions and its conversation history.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

Which ibl.ai agents work with Docusign eSignature data?

Which ibl.ai platform skills does a Docusign eSignature agent use?

What else should I know before connecting Docusign eSignature to an AI agent?

Is there an official Docusign eSignature MCP server?

Yes. Docusign publishes Docusign MCP Server.

You can register it on ibl.ai as an MCP server, or use the SKILL.md when you want the agent to call the Docusign eSignature REST API (v2.1) directly.

Who can get Docusign eSignature API credentials?

Anyone can open a free Docusign developer account and create an integration key under Apps and Keys. Moving an app to production accounts requires Docusign's go-live review.

Does Docusign eSignature data leave my infrastructure when an ibl.ai agent uses it?

On ibl.ai, you own all the code and the data. Self-hosted in your cloud or data center, the agent, its MCP connections and its conversation logs stay inside your perimeter.

Because the platform is model-agnostic, you can point the agent at a model you host, so Docusign eSignature records need not reach a third-party model provider.

Is the Docusign eSignature agent skill free to use?

Yes. The SKILL.md is a free download with no sign-up. It assumes you already have Docusign eSignature credentials, and your agreement with Docusign still governs how you use its API.

Which other data sources can an AI agent connect to alongside Docusign eSignature?

Which other Legal systems have a connector?

  • Clio Manage — Legal practice management system
  • iManage Work — Legal document and email management system
  • Ironclad — Contract lifecycle management system
  • LexisNexis — Legal research content and AI API
  • NetDocuments — Cloud legal document management system
  • PACER — U.S. federal court records system
  • RelativityOne — E-discovery and legal review platform
  • Westlaw — Legal research platform

Which other Financial Services systems have a connector?

Which other Enterprise systems have a connector?

Every connector, grouped by sector, is on the connectors hub.