---
name: iblai-connect-docusign
description: "Read and write Docusign eSignature data through the Docusign eSignature REST API (v2.1) and expose it to an ibl.ai agent as an MCP tool. Use when the user asks an agent to work with Docusign eSignature data, or to set up a Docusign eSignature MCP connection on ibl.ai."
metadata:
  kind: guide
---

# Docusign eSignature connector for AI agents

> A starting point maintained on ibl.ai at https://ibl.ai/developer/connectors/docusign — not part of the iblai/vibe repository. Checked against Docusign's documentation on October 20, 2026; test it against your own Docusign eSignature setup before you rely on it.

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.

## Auth & conventions

- **API:** Docusign eSignature REST API (v2.1) (REST). 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.
- **Base URL:** {base_uri}/restapi/v2.1/accounts/{accountId}/ where base_uri comes from the OAuth userinfo call (demo accounts use demo.docusign.net)
- **Access:** Public, self-serve. 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:** OAuth 2.0 authorization code; OAuth 2.0 JWT grant. 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.
- **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.
- Keep Docusign eSignature credentials in environment variables or the ibl.ai credential store. Never print a token in chat and never commit one to a file.
- Destructive or outward-facing calls are marked **Confirm with the user first** — do.

## Reads

- **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.

## Writes

- **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.

## Expose it to an ibl.ai agent (MCP)

Docusign publishes an official MCP server, Docusign MCP Server (https://developers.docusign.com/platform/mcp-server/). Register it below as-is, or host your own server that wraps the calls in this skill.

First install the ibl.ai platform skills and connect your organization (writes `IBLAI_ORG`, `IBLAI_USERNAME` and `IBLAI_API_KEY` to `.env`):

```bash
npx skills add iblai/vibe --all
# then, in your coding agent:
/iblai-api-login
```

Every call below sends `Authorization: Api-Token $IBLAI_API_KEY`.

1. **Register the server** — `POST https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mcp-servers/` with `name`, `url`, `transport` (`sse` | `websocket` | `streamable_http`) and `auth_type` (`none` | `token` | `oauth2`). Capture the returned `id`.
   - Docusign eSignature supports per-user OAuth: `auth_type=oauth2` with `auth_scope=user` and a linked `oauth_service` makes each person connect their own account in the chat. It needs an `auth_{provider}` credential in the organization's credential store first.
2. **Create the connection** — `POST https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mcp-server-connections/` with `server`, `scope` (`platform` | `mentor` | `user`), `auth_type`, and either `credentials` + `authorization_scheme` or a `connected_service` id for OAuth. Credentials are masked on read; never send a masked value back.
3. **Enable it on the agent** — `GET https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mentors/{agent_id}/settings/`, add `mcp-tool` to `tool_slugs` and the server id to `mcp_servers`, then `PATCH` the full lists back. They are replaced, not merged.

Full reference: https://ibl.ai/developer/platform/mcp/mcp-connections and the `/iblai-api-agent-mcp` skill.

## Example prompts

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

## Guardrails

- Envelopes often carry privileged or confidential agreements, and financial or personal data; sending is an outward, legally binding act that needs human approval.
- Request the narrowest Docusign eSignature scopes or role the task needs, and prefer a read-only credential for agents that only answer questions.
- Return the fields the user asked for, not whole records; do not paste personal data into chat that the user did not request.
- Before any write, show the user exactly what will change and wait for a yes.
- Respect the documented limits above: page through results and back off on rate-limit responses instead of retrying in a loop.

## References

- Docusign eSignature REST API: https://developers.docusign.com/docs/esign-rest-api/
- Docusign MCP Server: https://developers.docusign.com/platform/mcp-server/
- Docusign authentication overview: https://developers.docusign.com/platform/auth/
- Docusign MCP Server: https://developers.docusign.com/platform/mcp-server/
- This connector on ibl.ai: https://ibl.ai/developer/connectors/docusign
- ibl.ai MCP server connections: https://ibl.ai/developer/platform/mcp/mcp-connections