The Signable MCP server lets AI assistants and agents work with your Signable account. Once connected, you can ask your assistant to find envelopes, check whether they have been signed, find templates, and send envelopes for signature.
The Model Context Protocol (MCP) is an open standard that lets AI applications use tools provided by other services. AI products from Anthropic, OpenAI, Google and others can connect to MCP servers.
Add this URL to your AI client:
https://mcp.signable.app/mcp/signableFor step-by-step instructions for each AI client, see Connect an AI client.
| Task | Example prompt |
|---|---|
| Find envelopes and check their status | "Has the tenancy agreement for 23 Melbourne Road been signed?" |
| Find templates and their signer roles | "Which NDA templates do I have, and who needs to sign them?" |
| Send an envelope from a template | "Send the Tenancy Agreement template to John Doe as Tenant." |
See Example prompts for more ideas.
To connect to the Signable MCP server, you need:
- A Signable user on a company account. Sub-accounts cannot connect.
- A verified company email address.
- An AI client that supports remote MCP servers with OAuth sign-in. See Connect an AI client.
You do not need an API key. You log in with your usual Signable credentials and approve access.
Check your AI provider’s data policies. Information returned by the Signable MCP server, such as envelope titles and statuses, is passed to your AI provider.
Check your AI assistant’s permission settings. Envelopes sent through the MCP server are charged at your usual plan rate. Signable can’t control how your AI assistant or agent operates, including whether it asks for confirmation before sending. We can’t refund charges for envelopes it sends by mistake or without your approval.
Your AI assistant has the same access as you do in the Signable web app. It can only see envelopes and templates that belong to your company and are shared with you or your user groups.
- Connect an AI client – Set up Claude, ChatGPT, Codex and Gemini