Connect Docusign to OpenCode
Give OpenCode governed access to Docusign’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Docusign to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 1
Approve Docusign in Runlayer
Add Docusign from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Docusign’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode setup guide - 3
Sign in to Docusign
Each user signs in to Docusign with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Docusign from OpenCode
Docusign’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
30 Docusign tools in OpenCode
Runlayer policy decides which of these OpenCode users can call. 14 read data only and 6 can change or delete data.
Cancel workflow instance
Cancel a running workflow instance.
Create envelope
Creates a new Docusign envelope from an EXISTING Docusign template or from documents provided via a remote URL.
Create envelope from template
PRIMARY TOOL for sending Docusign agreements or envelopes for signature using templates.
Get account
Retrieve account information for a specific eSign account.
Get agreement details
Retrieve detailed information about a specific agreement
Get agreement filter skill
REQUIRED BEFORE A FILTERED getAllAgreements CALL: Call this skill before constructing the filter.
Get all agreements
Retrieves agreements for a Docusign account.
Get clm workflow definitions
Retrieve workflow definitions for a CLM account.
Control
What Runlayer can see and stop in OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Docusign call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more