Inkfree

What Inkfree MCP server does

Inkfree MCP server exposes an Inkfree account to an AI assistant through the Model Context Protocol. The hosted endpoint supports work with e-signature envelopes, documents, templates, signers, folders, sharing permissions, webforms, and reporting data.

Typical requests include finding envelopes that are awaiting signatures, checking a signer’s position and status, sending a draft, sending an envelope from a template, or sending separate envelopes to multiple recipients. The available operations also cover reminders, voiding, document download links, audit history, folder organization, and envelope access for colleagues.

Reports provide dashboard totals, status and funnel counts over a date range, and activity grouped by recipient, template, or user.

How it works

The service is hosted by SoftSages at https://api.inkfree.app/core/inkfree/mcp/. It uses Streamable HTTP rather than requiring a local process. A compatible client connects to the endpoint and completes OAuth 2.1 authorization with PKCE and dynamic client registration. The user signs in on Inkfree’s login page, so the password is not passed to the AI client.

After authorization, the client receives a short-lived token scoped to the user’s Inkfree account. Tool calls are limited to envelopes and templates that the account can access. Advertised scopes include mcp:read, mcp:write, and mcp:send.

MCP annotations identify read-only operations and flag actions such as sending, resending, voiding, deleting, and revoking access as destructive. Tools that email signers are marked as open-world operations, allowing clients that honor these annotations to request confirmation before acting.

Setup and configuration

No package installation or local server process is required. Add the hosted URL as a remote MCP server in the client, then authenticate with an Inkfree account. The README documents setup for Claude, Claude Code, ChatGPT, Cursor, VS Code with GitHub Copilot agent mode, and Cline.

For clients without a dedicated setup guide, use the same URL with Streamable HTTP. The endpoint returns 401 with a WWW-Authenticate header containing protected-resource metadata, enabling MCP clients that follow the authorization specification to discover the authorization server and register themselves.

An Inkfree account is required. To disconnect, remove the connector from the client. The hosted design means there are no server-specific environment variables to configure.

Tools and capabilities

The Inkfree MCP server provides 32 tools according to the repository metadata. Supported areas include:

• Listing and filtering envelopes by status
• Inspecting signer order and signing status
• Sending drafts or template-based envelopes
• Bulk-sending one template as separate envelopes
• Resending reminders and voiding envelopes
• Retrieving document download links and complete audit trails
• Creating and managing folders for envelopes and templates
• Moving, renaming, and deleting organized items
• Granting view-only envelope access, listing access, and revoking it
• Listing webforms and their linked templates
• Reading dashboard, funnel, recipient, template, and user activity reports

Limitations and notes

The repository contains documentation and a registry manifest, not the server implementation. The service is operated by SoftSages and is not open source. Access depends on the permissions of the connected Inkfree account, and every operation acts as that user.

Sending, resending, voiding, deleting, and revoking access can change account data or affect recipients. Clients should treat those operations accordingly and request user confirmation when supported. Disconnecting the client removes its connection, but account data remains governed by Inkfree’s policies and terms.