Fifteen MCP tools
Read, draft, upload, place fields, add signers, and manage contacts and templates.
MCP and AI agents
E-Signature for AI Agents (MCP Server)
Bond4Docs runs a hosted MCP server, so an AI assistant can read your documents and prepare new ones directly — while the act of sending a binding request stays with a person.
Free · No credit card · No signing limits
Short answer
Bond4Docs provides a hosted Model Context Protocol server at https://www.bond4docs.com/api/mcp, secured with OAuth 2.1, that connects AI agents such as Claude to your document workspace. It exposes fifteen tools covering listing and reading documents, creating drafts and structured agreements, uploading PDFs, placing fields, adding signers, and managing contacts, templates, and folders. Critically, there is no tool that sends a document for signature: an agent can draft and prepare a complete agreement, but a person must send it from the app. The MCP server is free, like every other Bond4Docs feature.
OAuth 2.1, scoped
The same scope model as the REST API, so an agent can be granted metadata access only.
An agent cannot send
No tool transmits a signature request. That step requires a person in the app.
Why this exists
Drafting an agreement is a genuinely good use of an AI assistant, and reviewing what is outstanding across a workspace is a natural question to ask one. Both require the assistant to reach the documents, which historically meant copying text into a chat window and losing every connection to the real record.
An MCP server closes that gap. The assistant works against the actual workspace, so a draft it produces is a real draft in your account with real fields and real signers attached, ready for you to review and send.
What the tools do
The fifteen tools split into reading, drafting, and organizing. Together they cover preparing a document end to end, short of transmission.
- Read — list_documents, get_document, read_document_text, list_templates, get_template, list_folders, list_contacts
- Draft — create_draft, create_agreement_draft, upload_document, update_document
- Prepare — add_signer, add_document_field, update_document_field
- Organize — create_contact
The line an agent cannot cross
There is no send-for-signature tool, and this is the single most important thing to understand about the integration. An agent can produce a complete, correctly prepared agreement with signers and fields in place. It cannot email that agreement to anyone.
The reason is that a signature request is a binding communication to a third party. Autonomous systems misfire — a misread instruction, a prompt injection in a document the agent read, a loop that runs twice — and the failure mode for sending is that real people receive real legal requests nobody reviewed. Preparation is reversible; transmission is not. So the product keeps a person at that step by construction, rather than by policy.
Connecting
Add https://www.bond4docs.com/api/mcp as a remote MCP server in a client that supports OAuth 2.1, such as Claude. You will be taken through consent, where you choose which scopes to grant, and the connection is then bound to your account.
Use the www form of the hostname. The apex domain redirects to www, and HTTP clients drop the Authorization header across a cross-host redirect, so the apex form authenticates during consent and then returns 401 on every actual call — which surfaces as a connector that appears to connect but reports no available tools.
Direct answers
Frequently asked questions
What is the Bond4Docs MCP server URL?
https://www.bond4docs.com/api/mcp. Use the www form — the apex domain redirects, and clients drop the Authorization header across that redirect, which makes the connection appear to succeed while every authenticated call fails.
Can an AI agent send a document for signature?
No. There is no send tool. An agent can draft an agreement, upload a PDF, place fields, and add signers, but transmitting the signature request requires a person acting in the app.
Which AI clients can connect?
Any client supporting remote MCP servers with OAuth 2.1, including Claude. Connection is made by adding the server URL and completing the OAuth consent flow.
Is the MCP server free?
Yes. Like every other Bond4Docs feature, the MCP server is included at no cost.
What can the agent actually see?
Only what the granted scopes permit. Document metadata and contents are separate scopes, so an agent can be given the ability to report on signing status without access to what the documents say.
Last reviewed .
Keep exploring
Free E-Signature API
A free REST API for document signing. Create drafts, upload PDFs, place fields, add signers, and read documents with scoped API keys.
Learn moreSecurity for Online Document Signing
Learn how Bond4Docs protects document-signing workflows with 2FA, secure links, encryption, audit logging, expirations, and completion certificates.
Learn moreFree Electronic Signature Features
Explore Bond4Docs features: PDF field editing, multiple recipients, templates, contacts, reminders, tracking, 2FA, audit history, and completion certificates.
Learn moreNo credit card required
Send your first document for free
Upload a PDF, add recipients, place fields, and start collecting electronic signatures without signing limits.
Create a free account