How to Connect Inkfree to Claude and ChatGPT

The Inkfree connector lets Claude, ChatGPT, and other AI tools that support the Model Context Protocol (MCP) work with your Inkfree account. Once it is connected, you can send, track, and tidy up sign requests by typing what you want in plain language. It is available on every Inkfree plan and needs no API key.

What Is MCP?

The Model Context Protocol is an open standard that lets an AI assistant use outside services through a defined set of tools. Inkfree runs an MCP server, so any MCP-compatible AI client can call Inkfree actions (send a request, list what is pending, download a signed file) on your behalf after you sign in and approve it. This is separate from the built-in AI Assistant, which works inside Inkfree itself.

What Is the Inkfree Connector URL?

Use this address in every AI client:

https://api.inkfree.app/core/inkfree/mcp/

Keep the trailing slash at the end. Sign-in happens through your normal Inkfree login, so there is no API key to copy.

How Do I Connect Inkfree to Claude?

1. In Claude, open Settings → Connectors.
2. Choose Add custom connector and name it, for example "Inkfree".
3. Paste the connector URL above and save.
4. Click Connect. Claude sends you to the Inkfree sign-in page.
5. Log in with your Inkfree account, review the consent screen, and click Approve.

You are returned to Claude with the connector switched on. Start a new chat and ask it to do something in Inkfree.

How Do I Connect Inkfree to ChatGPT?

ChatGPT supports custom MCP connectors in its settings. The exact labels depend on your ChatGPT plan and version, but the flow is the same:

1. Open ChatGPT Settings and go to the Connectors (or Apps) area.
2. Add a custom MCP connector and paste the same connector URL.
3. Sign in to Inkfree when prompted and click Approve on the consent screen.

Other MCP-compatible tools follow the same pattern: add a remote MCP server, paste the URL, then sign in and approve. Developers can find setup for Claude Code and VS Code, the full tool list, and how sign-in works in the Inkfree MCP server docs.

What Can I Ask It to Do?

The connector covers the day-to-day work of managing sign requests:

• Sign requests: send, bulk send, list, view details, resend, void, delete, rename, move into folders, create folders, download, and view the audit trail.
• Templates: list, send from a template, rename, move, delete, and organize into folders.
• Sharing: share a request with a colleague, see who it is shared with, and revoke access.
• Web forms: list your web forms, including the ones built from a given template.
• Reports: request counts in total, by date, or by status, plus recipient, template, user, and audit summaries.

A few prompts to try:

• "Send the NDA template to jane@acme.com and ask her to sign by Friday."
• "Which requests are still waiting on signatures this week?"
• "Void the request called Vendor Agreement Q3 and tell me who it was sent to."
• "How many requests did we complete last month, broken down by status?"

Is It Secure?

The connector signs in as you and works only inside your own Inkfree account. There is no API key to leak: access is granted through your normal Inkfree login and a consent screen. It follows the same ownership rules as the web app, so it cannot share an envelope you do not own. Deleting always needs an explicit confirmation, and a request that is still waiting on signatures has to be voided before it can be deleted.

Sends, voids, and shares made through the connector are recorded in the envelope's audit trail, the same as when you do them in the web app. You can disconnect at any time by removing the Inkfree connector in your AI client's settings.

Troubleshooting the Connection

• The sign-in page belongs to a different product. The URL is wrong. Remove the connector and add it again using https://api.inkfree.app/core/inkfree/mcp/ exactly.
• The connector will not connect or keeps failing. Check that the URL ends with a trailing slash. Leaving it off is the most common cause.
• An action is refused. Ask the AI to show you the error. Common causes are acting on a request you do not own, deleting a request that is still waiting on signatures (void it first), or deleting a folder that is not empty.

Questions about the built-in assistant rather than the connector? See the AI Assistant FAQ.