The Sign.Plus MCP Server lets AI assistants create envelopes, send documents for signature, manage templates, track signing status, and configure webhooks through the Model Context Protocol (MCP) — an open standard for connecting AI tools to external services.
Beta — The Sign.Plus MCP Server is currently in beta. Features, tool schemas, and authentication flows may change. Report issues to support@alohi.com.
API plan required — Access to the Sign.Plus API requires a Sign.Plus API plan. Non-API plans have access to sandbox but can’t send signature requests.
Read-only access to all eSignature operations (GET endpoints)
sign:all:edit
Full access to all eSignature operations (POST, PUT, DELETE endpoints)
Select both scopes for full MCP functionality. Use sign:all:read alone if you only need to view envelopes, templates, and signing status without creating or sending documents.
For production integrations, Sign.Plus supports the standard OAuth 2.0 authorization code flow. See the authentication documentation for the full setup guide.
from openai_agents import Agent, MCPServerSsesignplus_server = MCPServerSse( url="https://mcp.sign.plus/mcp", headers={"Authorization": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"},)agent = Agent( name="eSignature Assistant", instructions="Help the user send documents for signature and track signing progress.", mcp_servers=[signplus_server],)
Replace YOUR_PERSONAL_ACCESS_TOKEN with the PAT you created in the Authentication section. If you’re using OAuth, pass the access token obtained from the OAuth flow.
Assistant: I’ve created an envelope called “Contract”, uploaded the document, added Sarah as a signer, placed a signature field on page 2, and sent it. Sarah will receive an email with a signing link. The envelope ID is abc123def.
Assistant: I’ve created a new envelope from your “NDA” template and sent it to Joss Bodan at j.bodan@alohi.com. The envelope is now in progress with a daily reminder configured.
Assistant: The envelope “Contract” is still in progress. Sarah received the signing request at 2:15 PM today but hasn’t signed yet. The next reminder is scheduled for tomorrow.
API plan required — The Sign.Plus API is only available on API-enabled plans. A free sandbox is available for evaluation and testing on all plans.
Sandbox vs production — Create envelopes with "sandbox": true for testing. Sandbox envelopes don’t send real emails and aren’t billed. Some PATs may be restricted to sandbox-only mode — contact support@alohi.com to enable production envelope creation if needed.
No account creation via API — New user accounts must be created through the Sign.Plus web dashboard.
Annotation coordinates — Annotation placement uses percentage-based coordinates (0–100) relative to page dimensions. The y-axis is measured from the bottom of the page.
Rate limits — API requests are rate-limited. See the API documentation for current thresholds.
File formats — Supported document formats include PDF, DOCX, PNG, XLS, and more. Maximum file sizes apply per the API documentation.
Your PAT may have expired or lacks the required scopes. Generate a new token from Settings → Integrations in your Sign.Plus dashboard. Ensure the token includes both sign:all:read and sign:all:edit scopes.
Your PAT is restricted to sandbox mode. Sandbox envelopes are created for testing only and do not send real emails. Contact support@alohi.com to enable production envelope creation, or upgrade your plan configuration.
Annotation coordinates are expressed as percentages (0–100) of the page dimensions. Note that the y-axis is measured from the bottom of the page, not the top. For a signature field at 75% from the top, set y to approximately 25 (i.e., 100 - 75).
Ensure the envelope has at least one document, one recipient with the SIGNER role, and one required annotation (e.g., a signature field) assigned to that recipient before calling send_envelope.
