Build, test, and debug Docusign application integrations in Antigravity. This plugin supplies three reusable skills. It works without a Docusign account, MCP connection, or CLI for local code planning, inspection, and mock tests.
| Skill | Use it to |
|---|---|
/docusign-build |
Inspect an application and implement a signing or envelope-status feature using current documentation. |
/docusign-test |
Run relevant checks and distinguish local, mocked and real developer-account results. |
/docusign-debug |
Investigate an actual failure, make a focused fix and verify the result. |
For Agreement Manager and solution-package tasks, the plugin points to the existing Docusign CLI skills. It does not bundle or automatically install them. The reviewed CLI version and requirements appear in skills/docusign-build/references/cli-skills.md.
Clone the repository into a folder named docusign, then run the installation commands from its parent directory:
git clone https://github.com/docusign/docusign-antigravity-plugin.git docusignAlternatively, extract a plugin release package into a folder named docusign.
agy plugin validate --strict ./docusign
agy plugin install ./docusign
agy plugin listUse a current Antigravity CLI that supports --strict. This candidate passed with CLI 1.5.2; CLI 1.3.1 does not support that flag. Open your application project in Antigravity and start a fresh conversation after installation or updating.
Try:
/docusign-build Inspect this project and plan a template-based signing feature. Explain the authentication choice and information still needed. Use official sources. Do not edit files or make account calls yet.
Then use /docusign-test to verify the implementation or /docusign-debug with a sanitized failure. Review the proposed code and configuration before running a live workflow.
The skills are Markdown instructions. The optional diagnostic/probe scripts require Node.js 20 or newer. Your application's SDK/framework may have its own requirements. Network access is needed to retrieve current documentation and, if configured, contact Docusign. Docusign CLI requirements apply only if you choose its workflows.
Installation grants no Docusign account access. To make real API calls, configure your application's authentication for its API actor and client type. Keep secrets server-side and out of chat, source control and browser code. Test with a developer account, verified template roles/fields, an intended test recipient and explicit authorization before sending.
The default package has no active MCP definition. Skills and MCP can be used independently. If your environment already has a Docusign MCP connection, use it rather than creating a duplicate.
For an optional developer-token setup, work from a writable extracted copy of this package, before installing it:
node docusign/scripts/enable-sandbox.mjs
agy plugin validate --strict ./docusign
agy plugin install ./docusignIn Antigravity's plugin configuration, enter your own DOCUSIGN_ACCESS_TOKEN locally when prompted. The helper copies config/mcp_config.sandbox.json to the package root and refuses to overwrite an existing file. Installed plugin folders may be read-only; do not edit them or place secrets in the package.
The example connects only to https://mcp-d.docusign.com/mcp. Tokens expire and this token-based example does not refresh them. Native browser OAuth is a separate client configuration; the plugin does not ship a shared OAuth app registration or the author's test credentials. Confirm authenticated tool discovery before using tools. A connection working in one client does not prove every tool or authentication flow works.
To probe initialization and discovery only, provide a developer token through your local secret mechanism and run node docusign/scripts/check-sandbox.mjs. Missing credentials are reported as blocked. The probe never calls business tools or sends agreements. You do not need this probe for skill-only tasks.
There are no install hooks, background agents, telemetry collectors, or bundled credentials. The project diagnostic reads package metadata and checks local runtime/CLI availability. The optional MCP probe contacts the developer MCP service only when run with a token. Antigravity and any configured services handle the data you choose to share under their own settings and terms.
See VALIDATION.md. Local tests, sandbox signing and App/IDE reads have been exercised, but generated recommendations still require review. This package does not supply production application hosting or turn the separate sample's mock UI into a live signing app.
Documentation: https://developers.docusign.com Authentication: https://developers.docusign.com/platform/auth/ CLI skills: https://developers.docusign.com/docusign-cli/ai-tools/
Public developer guide: https://docs.google.com/document/d/e/2PACX-1vSc9_kaDDnKY2AVdw2iGexbgVnMdZEI9AuuDoM-HKZ13Dmx92tE5dsvEay1yXUyx0JYFqiwZKZYo3xr/pub