How to Send Documents for Signature From ChatGPT or Claude
How an MCP server lets you send documents for e-signature, check status and send reminders from ChatGPT or Claude, with your approval at every step.
More and more work starts in an AI assistant. You draft an email, summarize a meeting or plan a project in ChatGPT or Claude. Getting a document signed has usually meant leaving that chat, opening another app and doing the steps by hand. With ReadyInk's MCP server, you can do it right from the conversation.
What is an MCP server?
MCP, short for Model Context Protocol, is an open standard that lets AI assistants connect to outside tools in a structured, permissioned way. An MCP server tells the assistant which actions it can take in a product and what information each action needs.
ReadyInk's MCP server runs on the same API as our app. That means the assistant can do the same things you can, through your own account.
What you can do from the chat
- Prepare a request. "Send the Johnson lease to Maya Ruiz and Sam Lee for signature, Maya first."
- Use your templates. "Start a new NDA from our standard template for Acme Co."
- Check status. "What's still waiting on a signature?"
- Follow up. "Send a reminder to everyone who hasn't signed the Patel agreement."
- Check your balance. "How many tokens do we have left this month?"
You approve before anything is sent
The assistant prepares the request and shows you the document, the signers, the signing order and how many tokens it will use. Nothing is sent until you confirm. Every action taken through the MCP server is saved in the document's audit history, the same as actions in the app.
How to connect ReadyInk
- Sign in to your ReadyInk account at app.readyink.ai.
- In ChatGPT or Claude, open the settings for connectors or integrations and add ReadyInk.
- Approve the connection with your ReadyInk sign-in.
- Start a new chat and ask the assistant to send a document.
The exact menu names can change as ChatGPT and Claude update their apps, so check each assistant's help pages if a step looks different.
Tips for good results
- Name templates clearly. "Standard NDA" and "Residential lease, 12 months" are easier for an assistant to find than "Doc v3."
- Be specific about signers. Include names, emails and signing order.
- Review the summary. Check the signers and token count before you confirm.
Prefer code?
Everything the MCP server does is also available through the ReadyInk API, including templates, signing requests, webhooks, audit history and token balances.