Limitations and Workarounds | Docusign

Does envelope search support fuzzy or semantic search?

No. Envelope search does not support reliable fuzzy or semantic search, especially across large envelope sets.

Workaround: Use precise search terms and expect occasional incomplete or inaccurate results. Narrow the query using specific customer, account, date range, email subject, email address, username, email body, envelope status, or other supported filters.
Are there any limitations when analyzing large agreement sets?

Yes. Large agreement-corpus analysis is limited by Agreement Manager API pagination, which means a single request cannot retrieve or process the entire corpus at once.

Workaround: Scope the request to a defined subset by combining filters such as customer, date range, status, or agreement type to reduce the result scope. Make sure the response reflects the scoped query and may not represent the entire corpus.
Can admins control read/write tool access by tool set or user group?

No. Granular administrative controls for restricting read and write tool sets by user groups are not supported within Docusign admin settings. At present, administrators can only toggle overall MCP access on or off.

Workaround: Currently, no specific workaround exists to provide granular controls, though support is scheduled for a subsequent release. Consult your AI provider’s documentation, as select third-party LLMs provide organization-level restriction settings. See Anthropic (Claude), OpenAI (ChatGPT), Slack (Slackbot) for more information.
Are MCP-specific audit logs available at GA?

No. MCP-specific audit logs will not be available at General Availability (GA).

Workaround: Operations performed through MCP are recorded in the existing eSign API audit logs.
Can I upload custom documents when using template-based envelopes?

No. Custom document upload is not supported for template-based envelopes.

Workaround: No workaround is available at this time.
Does integration-key onboarding require any upfront steps?

Yes. Integration-key onboarding requires upfront MCP allowlisting by submitting a form before the key can be used with the MCP server.

Workaround: Onboard the integration key to the supported MCP client during IK creation and submit the MCP-server allowlisting form. Refer go-live with production account section for more details.
Is the MCP server available in languages other than English?

The MCP server is released in English and the MCP apps interface is in English only. At GA, language support and response quality for non-English interactions are handled by the connected third-party LLM.

Workaround: Response quality depends on the connected AI assistant’s language capabilities. Docusign has tested French, Spanish, Portuguese, German, and Japanese. Customers should validate accuracy for other languages.

Integration Key Not Approved After Docusign MCP General Availability

Docusign MCP reached General Availability (GA) on September 30, 2026.

As part of the GA release, Docusign introduced an approval requirement for integration keys (IKs) used with the Docusign MCP server when you go-live with the production accounts . This article explains who is affected, what the error means, and the exact steps to resolve it.

If your Integration Key (IK) (created in production Docusign account) was used to make any Docusign MCP tool calls in the 30 days before September 30, 2026 (September 1–30, 2026), your integration key is automatically approved and continues to work without interruption after GA.

Production IK Usage (Sept 1–30, 2026)	Post-GA Status	Impact on MCP Tool Calls
Active (Made call(s) within 30 days prior to Sept 30)	Automatically Approved	Works without interruption
Inactive (No calls made during this period)	Automatically Disabled	Calls will fail and return an error. Submit this form to get access.
Demo Account IK (Created in demo Docusign account)	No Change	Continues to work as normal

If your integration key is disabled, your AI assistant returns the following error:

This integration is not currently approved for use with Docusign MCP.
Requests from this integration key will be denied until it is approved by Docusign.

1. If you are the Docusign administrator who manages this integration:
Submit a request to Docusign to approve the integration key for use
with Docusign MCP.

2. If you are not the administrator for this integration: Contact your Docusign administrator and ask them to submit the approval request to the above link.

If you are the Docusign administrator for this integration,

Submit an approval request directly to Docusign using this form. Once submitted, the Docusign team reviews your request and re-enables the integration key.

If you are not the Docusign administrator for this integration,

You cannot submit the approval request yourself. Contact the Docusign administrator in your organization and ask them to submit the request using the link above.

**Frequently Asked Questions

My integration key was active before September 2026. Why was it disabled?**

Only integration keys that made MCP tool calls between September 1–30, 2026 were automatically approved at GA. If your integration key was not used during that specific 30-day window, even if it was used before, it is marked as disabled at GA.

Do I need to create a new integration key?

No. You do not need to create a new integration key. Submit the approval request for your existing integration key. Once approved, it works as before.

Can I check whether my integration key is active before attempting to use it?

There is currently no self-serve status check. If your integration key is disabled, you will encounter the error described in this article when you attempt to use the MCP server.