Skip to main content
InkfreeInkfree home
Get an API key

MCP server

Inkfree MCP server

Connect AI assistants like Claude, ChatGPT, Claude Code, and VS Code to Inkfree over the Model Context Protocol, so they can send, track, and manage signature requests in your account.

Last updated:

On this page

What the Inkfree MCP server does

The Inkfree MCP server lets an AI assistant work in your Inkfree account through 32 tools: listing and sending sign requests, sending from templates, sending reminders, voiding, downloading signed documents, sharing, organizing folders, and running reports.

It is the developer view of the Inkfree AI connector. If you only want to set it up in Claude or ChatGPT, the help article walks through it without the protocol detail. It is available on every Inkfree plan, including Free.

How MCP works

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to outside systems. A server publishes a set of named tools, each with a description and a JSON Schema for its arguments. An MCP client, such as Claude or ChatGPT, reads that list and decides which tool to call to carry out what you asked for.

With Inkfree, the sequence for a prompt like "remind everyone who has not signed the lease" looks like this:

  1. The client calls mcp_inkfree_sign_requests_list to find the pending lease envelope.
  2. It calls mcp_inkfree_sign_request_resend with that envelope's requestId.
  3. Inkfree sends the reminder emails and returns the result, which the assistant summarizes for you.

Every call runs as the Inkfree user who signed in. There is no account or tenant argument on any tool: the account comes from your sign-in, so a tool can never reach another organization's data.

What is the Inkfree MCP server URL?

The server uses the streamable HTTP transport at a single remote address. Add it to any MCP-compatible client:

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

Keep the trailing slash

The URL must end in /mcp/. Without the final slash the client cannot connect, which is the most common setup mistake.

The server is an OAuth 2.1 protected resource. Clients sign in with the authorization code flow and PKCE, so you log in with your usual Inkfree account and approve access on a consent screen. No API key is pasted into the client. See Connecting a client for the details.

What can the AI do in my account?

Every call runs as the Inkfree user who signed in and is limited to that user's account. The tools call the same Inkfree services as the web app, so the same ownership rules apply: for example, only an envelope's owner or an admin can share it.

  • Read tools (lists, details, audit trails, downloads, reports) change nothing.
  • Write tools (void, resend, rename, move, share, delete, create folder) change one item at a time. Deleting an envelope or template needs an explicit confirm=true argument, and a Pending envelope must be voided before it can be deleted.
  • Send tools (send, bulk send, send from template) email signers.

Sends, voids, and shares are recorded in the envelope's audit trail, the same as when you do them in the web app. Calls are rate limited per session and per account.

Tool groups

The 32 tools fall into five groups. The Available tools page lists each one with its required arguments.

Sign requests13Find, send, follow up on, and organize envelopes. Envelope folders are a separate tree from template folders.Templates7Browse reusable templates and send new envelopes from them. Signing order, fields, and reminders come from the template.Sharing3Give a colleague view-only access to an envelope without making them a signer.Web forms2Public form pages linked to templates.Reports7Counts and activity summaries. Every report tool is read-only.

Feedback

If a tool you need is missing, a description leads an assistant to the wrong tool, or a client will not connect, tell us through the contact form and include the client name and the prompt you used.