MCP server

JustDocs runs a remote Model Context Protocol server. With it, an AI agent can find your workspace's templates or create them, start documents, and ask to send them for signature or for details. A person approves each send first.

Endpoint	https://tryjustdocs.com/mcp
Transport	Streamable HTTP, stateless. Every message is a POST, and replies are JSON.
Authentication	Sign in with OAuth, or an agent key. Either is sent as Authorization: Bearer on every request.
Registry	com.tryjustdocs/justdocs in the official MCP Registry
Tools	14. Each one is a REST operation with the same name.
Plan	Every plan. Below Teams & Platform, up to 3 active agent keys per workspace

How it works

1. You give the agent an agent key, and choose what it may do: in your personal workspace, or in a team where you're an owner or admin. Either you make the key on the workspace's API & agents page, or the agent's client signs in with OAuth and you approve it on a JustDocs page, which makes the key for that app.
2. The agent's client connects to /mcp with the key or its access token. It sees only the tools its permissions allow.
3. The agent reads or creates templates, starts documents and creates signing requests or intake links, as the person who made the key, in the one workspace the key belongs to.
4. When it asks to send, JustDocs holds the send as an approval and tells the agent nothing has gone out yet.
5. The workspace's owner, or a team's owner or admin, approves or declines it on the workspace's Approvals page. JustDocs then sends it, checking the key and its limits again, and the agent sees the result through get_approval.

Recipients sign from the private link JustDocs emails them. No tool signs, and no tool returns that link.

The tools

Tool	Does
get_workspace	Learn which workspace the key works in, its plan, and whether its sends wait for approval
list_templates, get_template	Find a template and learn its fill-ins, roles and questions
create_template	Make a template from text or a library entry, when there's no suitable one. It emails no one. See Create a template.
start_document, get_document	Start a document from a template, filled in
create_signing_request, send_signing_request	Prepare a request, and ask to send it
list_signing_requests, get_signing_request	Follow requests and each recipient's progress
void_signing_request	Cancel a sent request that isn't complete. This takes effect at once, without approval.
create_intake_request, get_intake_request	Ask someone for the details that fill the documents
get_approval	See whether a person approved what the agent asked to send

Next

• Connect a client Claude, ChatGPT, Cursor, VS Code, connector platforms, or any MCP client.
• Sign in with OAuth What the person approving sees, tokens, and the endpoints for client developers.
• Tools Every input, permission and annotation.
• Safety model Approvals, limits and what an agent can never do.
• Troubleshooting What each error means and how to fix it.