Docracy

What docracy does

The docracy MCP server exposes Docracy document operations to MCP-compatible AI clients. The documented use case is read-oriented: an agent can search documents and check the status of a signing process. This fits workflows where a user wants to locate an agreement, determine whether signing is complete, or inspect the current state of a document from an AI interface.

Docracy itself supports electronic signing for simple agreements. Documents can be uploaded as PDFs or created from templates, then assigned to signers with fields such as signatures, initials, text, dates, checkboxes, and dropdowns. The broader Docracy product supports sequential or parallel signing, status pages, completion certificates, and automatic email delivery of completed documents. The MCP listing should be understood as access to the documented search and status capabilities rather than a claim that every Docracy feature is exposed as an MCP tool.

How it works

The connector is implemented as a remote MCP server in the repository's apps/connector application. Clients connect through the published endpoint at https://docracy.io/mcp. The README names Claude, ChatGPT, Grok, Perplexity, and Cursor as connection targets; this listing identifies the supported client slugs available in the directory.

Docracy stores free or anonymous document state in Cloudflare KV and PDF files in Cloudflare R2. Paid workspaces also use Cloudflare D1 for derived indexing. D1 is not the source of truth, and anonymous documents do not depend on it. Those storage details explain the application's architecture but do not imply that the MCP connector directly exposes storage operations.

Setup and configuration

For the hosted service, connect an MCP client to the Docracy MCP endpoint. For local development, install dependencies, copy apps/worker/.dev.vars.example to apps/worker/.dev.vars, and start the worker, web app, and connector with the repository's development scripts. The local development commands are npm install, npm run dev:worker, npm run dev:web, and npm run dev:connector.

A deployment requires a token secret shared with the connector and worker, plus the public application URL. The full application setup also calls for a Resend API key and Cloudflare KV, R2, and D1 resources. Without RESEND_API_KEY, local outgoing email is written to the worker console instead. Secrets and local variable files should not be committed.

Tools and capabilities

The docracy MCP server is documented for two practical operations:

• Search Docracy documents.
• Check document signing status.

These capabilities can help an agent answer questions about document location and progress.

Limitations and notes

Free Docracy documents are automatically deleted after a short retention period: up to nine days, or sooner after completion and delivery. Free use also limits documents to two signers and two CC recipients. Paid workspaces provide longer or custom retention options and additional account features, but MCP and API access is revoked when paid status is removed.

The repository marks its license as TBD, so no open-source license should be assumed. The docracy MCP server also depends on Docracy account or plan availability for features outside the basic anonymous signing flow. Treat the MCP endpoint as a way to query the documented Docracy data and status functions, not as a replacement for the complete Docracy dashboard or signing interface.