Get it signed from your assistant.

Three steps, nothing more.

Talk to your assistant as you always do. Khatm handles the rest, and you keep the final word.

1. Connect Add the connector address, then click “Allow” in Khatm. No key to copy.
2. Ask “Send this contract to Alice for signature.” The assistant prepares a draft: document, signers and fields.
3. Confirm You check the PDF and its fields in Khatm, then confirm. The signer receives their link by email.

The assistant prepares. You decide.

An agent can make mistakes. Khatm is built so that a mistake stays a draft, and so that you can cut off access at any time.

Connect it in a minute.

The server is hosted by Khatm. Your assistant opens a Khatm page: you sign in, read what the agent will be able to do, then click “Allow”.

Connector address : https://www.khatm.io/mcp

Claude

• Open Settings → Connectors.
• Click “Add custom connector”.
• Paste the address below, then authorize Khatm.

ChatGPT

• Turn on developer mode in settings.
• Open Settings → Connectors → Create, with OAuth authentication.
• Paste the address below, then authorize Khatm.

Claude Code

• Run the command below in your terminal.
• Type /mcp in Claude Code to sign in.
• Authorize Khatm on the page that opens.

Thirteen tools, a clear scope.

The assistant has what it needs to prepare and follow a request. It never signs.

Prepare

A draft, never a send.

• list_templates : Your templates and their roles
• list_email_templates : Your branded emails
• prepare_signature_request : A draft from a template
• start_pdf_upload : A single-use upload address
• prepare_signature_request_from_pdf : A draft from the assistant’s PDF
• set_signature_fields : Each signer’s fields

Act

Sensitive actions wait for your approval.

• send_signature_request : Sends the request to the signers
• replace_signer : Hands a role to someone else
• cancel_signature_request : Cancels a request
• remind_signers : Reminds those who haven’t signed
• check_confirmation : Your decision on an action

Follow

Statuses and signers, nothing more.

• get_signature_request : Where a request stands
• list_signature_requests : Your requests, by status

For your integrations, a sandbox key.

Connect the same server to your own agents, on test documents with no legal value.

Frequently asked questions.

Which assistants are compatible?

Claude (claude.ai, Claude Desktop and Claude Code), ChatGPT in developer mode, and any client that supports MCP with OAuth.

Can the assistant sign for me?

No. It prepares and follows requests. Each signer signs personally, from the link received by email; no tool returns that link.

Does the signed document have legal value?

Not yet. Requests prepared by an assistant currently go through the test environment: the PDF is signed with a test certificate that has no legal value, and files are deleted 10 days after upload. Use sample documents; going to production is prepared with you.

What does the assistant see of my documents?

The statuses, names and emails of the signers. It receives no signing link, no field positions and no document content. The only PDF it passes on is the one it drafted with you.

Can I send ten contracts at once?

Yes. The assistant prepares each request; the confirmation page lists them all, checked. Untick the ones you are keeping for later and confirm the rest in one click.

Do I need a Khatm account?

Yes. The assistant acts on your account’s behalf: you sign in to Khatm when you authorize the agent, and its requests appear in your workspace.

How do I remove access?

In Khatm, open “Connected agents” and disconnect the agent. You also find the history of its actions there.

Your assistant already drafts your contracts. Now it can get them signed.

Connect Khatm in a minute. You confirm every send, and you can remove access at any time.