Documentation Index

Fetch the complete documentation index at: https://apidoc.sign.plus/llms.txt

Use this file to discover all available pages before exploring further.

​

Sign.Plus MCP Server

​

MCP server URL

https://mcp.sign.plus/mcp

​

What you can do

​

Prerequisites

1. An active Sign.Plus API plan or an active Sign.Plus Sandbox
2. A Personal Access Token (PAT) or OAuth 2.0 credentials — How to create a PAT
3. At least one document or template to work with

​

Authentication

​

Personal Access Tokens (PAT)

​

Available scopes

​

OAuth 2.0

​

Connecting to an MCP client

​

Generic MCP configuration

{
  "mcpServers": {
    "signplus": {
      "type": "url",
      "url": "https://mcp.sign.plus/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"
      }
    }
  }
}

​

Using with the Anthropic API (MCP Connector)

import anthropic

client = anthropic.Anthropic()

response = client.beta.messages.create(
    model="claude-sonnet-4-6",
    max_tokens=1024,
    betas=["mcp-client-2025-11-20"],
    mcp_servers=[
        {
            "type": "url",
            "url": "https://mcp.sign.plus/mcp",
            "name": "signplus",
            "authorization_token": "YOUR_PERSONAL_ACCESS_TOKEN",
        }
    ],
    messages=[
        {"role": "user", "content": "Send the NDA template to john@example.com for signature"}
    ],
)

​

Using with OpenAI Agents SDK

from openai_agents import Agent, MCPServerSse

signplus_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],
)

​

Available tools

​

Envelopes

​

Documents

​

Annotations

​

Signing Steps

​

Attachments

​

Templates

​

Webhooks

​

Usage examples

​

Send a document for signature

You: Send the attached contract to sarah@example.com for signature
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.

​

Create from a template

You: Use the NDA template and send it to j.doe@example.com
Assistant: I’ve created a new envelope from your “NDA” template and sent it to John Doe at j.doe@example.com. The envelope is now in progress with a daily reminder configured.

​

Check signing status

You: Has Sarah signed the contract yet?
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.

​

List your templates

You: What templates do I have?
Assistant: You have 11 templates:

1. Letter-of-Intent-to-Sue — 2 pages, 1 signer
   
2. Technical SEO Audit Report — 3 pages, 1 signer
   
3. UBS Factsheet (multi-signer) — 3 pages, 4 recipients across 3 signing steps
   …and 8 more.

​

Download signed documents

You: Download the signed copy of the NDA
Assistant: Here’s the signed NDA document. All parties have completed signing and the certificate of completion is also available.

​

API reference

​

SDKs

​

Security and compliance

• Encryption: AES-256 at rest, TLS 1.3+ in transit, unique encryption keys per user
• Certifications: ISO 27001, SOC 2 Type 2, HIPAA (with BAA), PCI DSS
• eSignature compliance: ESIGN Act, eIDAS (SES and QES), ZertES
• Privacy: GDPR, CCPA
• Access control: SSO, 2FA, role-based permissions, fine-grained PAT scopes
• Audit trails: Tamper-proof certificate of completion for every signed document

​

Limitations

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

​

Troubleshooting

​

”Invalid token” or 401 Unauthorized

​

”Non-sandbox envelopes are not allowed”

​

Annotation appears in the wrong position

​

Envelope stuck in DRAFT status

​

Getting help

• Help Center: help.alohi.com
• API Support: support@alohi.com
• Enterprise Sales: alohi.com/contact-sales