How to Sign Documents Directly from ChatGPT or Claude: The okdoc MCP Guide

TL;DR: You can now create, send and track e-signature documents directly from ChatGPT or Claude, without opening okdoc at all. Add okdoc as a connector in your assistant's settings (a one-minute, URL-only setup, no code), approve a secure OAuth 2.1 login, and from that moment you just type things like "draft a lease agreement and send it to Dana for signature." The assistant runs okdoc's 38 tools for you: document creation, sending, contract analysis, reminders, sign-and-pay, and analytics.

Until now, getting a client to sign looked like this: open a word processor, draft the document, export a PDF, log into an e-signature platform, upload, place signature fields, send. Five tools, fifteen minutes, and plenty of room for mistakes.

There is now a shorter path. okdoc, an AI-native e-signature platform, has launched an official MCP connector that plugs the entire system directly into ChatGPT and Claude. This guide explains what that means in practice, how to connect step by step, and what you can do with it today.

What is MCP and why does it matter?

MCP (Model Context Protocol) is an open protocol that lets AI assistants like ChatGPT and Claude connect to external systems and perform real actions in them: read data, create documents, send things. Think of it as a universal power socket for AI: any system that supports the protocol can plug into any assistant that supports it.

Anthropic (the company behind Claude) introduced the protocol in November 2024, and in March 2025 OpenAI officially adopted it for ChatGPT as well. Since then it has become the industry standard for connecting AI assistants to business software.

The practical meaning for you: your assistant stops being an advisor that only talks and becomes a worker that executes. When you type "send the agreement for signature," the document actually goes out, from your own okdoc account, fully logged and tracked.

What can you do with okdoc inside ChatGPT and Claude?

The okdoc connector exposes 38 tools to your assistant, covering the full lifecycle of a document: creation, sending, tracking, signing and payment collection. All of it in one conversation, in any language.

The main capabilities:

• AI document generation: draft a lease, a proposal, a service agreement or an NDA with a single prompt, created directly in your okdoc account.
• Send for signature: add recipients, signing order and signature fields, and deliver by email, WhatsApp or SMS.
• Tracking and reminders: ask who signed, who opened and who is ignoring you, then send a polite reminder without leaving the chat.
• Contract analysis: upload a contract you received and have the assistant analyze it through okdoc: risky clauses, critical dates, obligations.
• Sign and pay: attach a payment request to a document so your client signs and pays on the same screen.
• Bulk send: get dozens of clients to sign the same document in one action, for example an updated policy or an annual agreement.
• Analytics: ask how many documents were signed this month, what your completion rate is, and how much money was collected through documents.

How do you connect okdoc to Claude?

Connecting to Claude means pasting one URL in settings. No installation, no code, under a minute:

1. Open Claude.ai (web or app) and click Settings. 2. Choose Connectors from the menu. 3. Click Add custom connector. 4. Paste the URL: `https://okdocai.com/api/mcp` 5. Click Add, then Connect. A secure login to your okdoc account opens (no account yet? You can sign up free on the spot). 6. Approve the permissions and you are done. okdoc is now available in every Claude conversation.

From that point Claude decides on its own when to use okdoc. Type "prepare an NDA and send it to Joe" and Claude picks the right tools automatically.

How do you connect okdoc to ChatGPT?

In ChatGPT the connection happens in the Connectors screen under Developer mode, again with a single URL. Note that this option is available on paid plans:

1. Open ChatGPT and click Settings. 2. Choose Apps & Connectors. 3. Scroll down, open Advanced settings and enable Developer mode (if it is not already on). 4. Go back to the Connectors screen and click Create connector. 5. Give it a name (for example okdoc) and paste the MCP server URL: `https://okdocai.com/api/mcp` 6. Under Authentication choose OAuth, then click Create. 7. Approve the okdoc login, and enable the connector in a conversation from the tools menu.

From here, any ChatGPT conversation can end with a signed document in your client's inbox.

What can you actually ask for? Real examples

Anything you would normally do in the okdoc interface can now be requested in one sentence. Prompts that work today:

• "Draft a 12-month lease agreement for an apartment in Tel Aviv, rent 6,500 NIS, and send it to Dana Cohen for signature by email."
• "Who hasn't signed this week? Send everyone a reminder."
• "Analyze the contract I attached and flag any problematic clauses before I sign."
• "Create a 15,000 NIS website project proposal with a 30% deposit payment request at signing."
• "Take my service agreement template and send it to the three new clients on this list."
• "How many documents were signed this month, and how does the completion rate compare to last month?"
• "Prepare an NDA with Acme Corp and add me as the second signer."
• "Move all signed 2025 agreements into a new folder called Archive."

Notice the pattern: you describe a business outcome, not software steps. The assistant does the translation.

Is it secure? What about permissions and privacy?

Yes. The okdoc connector is built on the MCP security standard: OAuth 2.1 authentication with PKCE, no shared passwords and no API keys floating around your chat.

In practice this means:

• You log in to your own account. During setup you are redirected to okdoc's secure login page, authenticate directly with okdoc, and the assistant receives a limited access token. Your password is never exposed to ChatGPT or Claude.
• PKCE built in. A mechanism that prevents interception of the login flow, in apps and browsers alike.
• Organization-level permissions. The assistant can only access what the logged-in user is allowed to see inside okdoc. A team member sees their team's documents, not the whole company's.
• Full audit trail. Every action the assistant performs is recorded in okdoc's activity log, exactly like an action taken in the interface. You can always see what was done, when, and by whom.
• One-click disconnect. Revoke access at any moment, from the assistant's Connectors screen or from your okdoc account settings.

And of course, the signatures themselves remain secure, verified digital signatures, like any document sent from okdoc. If you want to go deeper into how digital signatures work and their legal standing, see our guide to digital signatures.

Who is this most useful for?

Anyone who signs clients regularly and already lives in ChatGPT or Claude. If the assistant is open on your screen anyway, there is no reason to leave it to get a signature.

Common scenarios:

• Lawyers and consulting firms: draft in the chat, send for signature, and analyze incoming contracts in the same window.
• Freelancers and agencies: proposal, work agreement and deposit request in one prompt, straight from the client conversation.
• Real estate agents and property managers: lease and exclusivity agreements sent over WhatsApp mid-call.
• Office and finance managers: bulk-send annual documents, track signatures, automate reminders.

Frequently asked questions

Do I need to know how to code? No. Setup is pasting one URL into Claude or ChatGPT settings and approving a login. No installation, no code, no servers.

Does it cost extra? The connector is included in all okdoc plans, including the free one. On the assistant side, custom connectors are available on Claude's paid plans, and ChatGPT requires a paid account with Developer mode.

Are signatures sent through ChatGPT legally valid? Yes. The document is sent and signed inside okdoc itself, with the same audit trail, signer verification and completion certificate as a document sent from the web interface. The assistant is just another way to operate the system.

Can the assistant sign on my client's behalf? No. The assistant can prepare and send documents, but the signature itself is always made by the signer, on their own device, after verification. That is a deliberate security principle.

Which languages are supported? Any language your assistant speaks. You can prompt in English and generate documents in English, Hebrew, or both, including full RTL documents.

How is this different from asking plain ChatGPT to write a contract? Plain ChatGPT produces text you still have to copy, format and send yourself. With the okdoc connector, the document is created as a real document in your account, with signature fields, recipients, tracking and payment. The difference between a draft and a closed deal.

Which clients are supported besides ChatGPT and Claude? Any client that supports remote MCP with OAuth, including Claude Desktop, Claude Code and other MCP-compatible tools. The URL is the same everywhere: `https://okdocai.com/api/mcp`

What happens if I ask for something I don't have permission for? The action is simply blocked. The connector respects your organization's permission structure in okdoc, and the assistant gets a clean error instead of access to the data.

Bottom line

Signing clients is no longer a five-tool process. Connect okdoc to ChatGPT or Claude once, and from then on every document, from drafting to signature to payment, closes in a single sentence in your chat.

Want to try it? Full details, including the connection URL and a walkthrough of all 38 tools, are on the okdoc inside ChatGPT and Claude page. No account yet? Sign up for okdoc free and get your first document signed today.