Docflare
Server Details
Send PDFs for e-signature from your AI assistant. Upload a PDF, add signers, place fields and preview it; it sends only after you approve. List documents by status and get the signed copy. OAuth sign-in; works on every Docflare plan.
- Status
- Healthy
- Uptime
- 50.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 12 tools
Most tools are clearly separable by resource+action, and the descriptions actively disambiguate the tricky pairs (open_upload_pad is explicitly a fallback for when upload_document's link is blocked; prepare_document handles recipients/settings while edit_document handles page content). The main residual overlap is document_status vs get_document, which both report status and signer progress for a single document, and prepare_document vs edit_document, which both return the same preview object.
Eleven of twelve tools follow a clean verb_noun pattern (get_document, list_recipients, send_document, open_signature_pad, etc.) with consistent scope suffixes like _document/_recipient. document_status is the lone noun-only outlier, a minor deviation rather than a different convention.
Twelve tools is well within a healthy range for a document-signing server, and each one maps to a distinct workflow step (upload, prepare, edit, preview, send, track, archive). The two pad tools exist for concrete fallback cases rather than padding the surface.
The happy path is fully covered end to end: create draft, set recipients/settings, place fields, preview, send, and track signer progress, plus recipient lookup and draft archiving. However, there is no way to void or cancel an in-flight document, no manual reminder trigger, no duplicate/template operation, and no explicit download of the signed file beyond a link in status output — gaps that will bite agents handling real post-send requests.
Available Tools
12 toolsarchive_documentArchive a draftAInspect
Moves a draft the user no longer wants to the trash in Docflare, where they can restore it. Only drafts: a sent document stays.
Inputs: id (required).
document_statusCheck a documentARead-onlyInspect
Tells where documents stand: draft, waiting for signatures, completed, declined or expired, with each signer's progress and, once everyone has signed, a link to the signed copy. Give the id of one document, or list them newest first, 10 a page, narrowed by status or by part of the name. The answer gives total, page and more, which is true while further pages remain.
Inputs: id, page, search, status.
edit_documentEdit a documentADestructiveInspect
Changes what is on a draft's pages: its fields, signatures included, its text and its lines, and whether signers share one copy or each get their own (type). Fields a signer fills need the signers, which prepare_document adds. Each list holds changes: an item without id adds one, an item with id changes only what it sends, and an item with id and delete true removes it. Ids come from get_document (page gives one page's text and lines) and from the added list of earlier answers. Positions are shares of the page width and height, from the top left. Every text on a page, the PDF's own included, can be moved, changed or deleted by its id. New text goes where it is placed, even over other text: the answer's notes name any text that overlaps other text, and the added list gives where each new text ends. A field goes on a line by the line's id, beside text on the page, at page, x and y, or in a free spot at the bottom of the last page. A field that does not sit on a line gets a line drawn under it, except a checkbox, and moving or deleting the field moves or deletes that line. With more than one signer, fields are placed once type is set: on a shared copy each field a signer fills names its signer by email, and when each gets their own copy no field names a signer. A detail Docflare fills in is a variable inside text. These are the only variables: {document.name}, {sender.name}, {sender.email}, {document.sent_date}, and a recipient's full_name, first_name, last_name, email, phone, company, job_title, street_address, city, postal_code, state_region, country, written {recipient1.full_name} with the signer's number from the preview on a shared copy, and {recipient.full_name} when each signer gets their own copy or there is one signer. get_document and every preview list the variables this document can use now, with what each shows (one value per signer, in order, when each gets their own copy); a variable left out has no value yet and would print nothing. Any other {name.name} is refused; the date a signer signs is a date field. On a document the user signs themselves (signed_by_sender), every field is the user's and takes its value now, saved for a signature or initials, which applies the user's saved one; no field names a signer, and the text uses no recipient variables. Variable fields from before become such text, except the reference, completed date and signed date, which stay fields. Nothing is sent. The answer is the same preview, preview_url and review_token as prepare_document gives.
Inputs: id (required), type, lines, texts, +1 more.
get_documentGet a documentARead-onlyInspect
Gives every detail of one document: its status, who signs it and who gets a copy, each signer's progress (invited, viewed, signed or declined with the reason, reminders, delivery problems), how it was or will be sent (delivery, signing order, email, expiry, reminders, what recipients may download, which prepare_document changes for a draft), its fields with their ids and places, and the signed copy once complete. For a draft it also lists the text on its pages, the PDF's own included, and the lines a field can sit on, each with an id for edit_document, the text changes made so far, and, with page, that page's text and lines in full. Ids come from document_status.
Inputs: id (required), page.
get_recipientGet a recipientARead-onlyInspect
Shows one person saved in the current Docflare workspace: their details, how many documents they signed, have still to open or sign, or declined, and those documents newest first, 10 a page, each with its document id and where it stands for them. Use it for questions such as whether someone signed a document or what is still waiting on them. The id comes from list_recipients.
Inputs: id (required), page, search, status.
list_recipientsFind recipientsARead-onlyInspect
Finds the people saved in the current Docflare workspace: everyone a document went to and everyone added on its Recipients page, newest first, 10 a page. When the user names someone without giving an email, search for them here before asking for one: a single match is that person, so use their email; with several, ask which one; with none, which may be a typo, search again with one word or part of one, such as "Koch", and ask for the email only when that finds nobody either. Every word of the search must match their name, email or company, so a full name, a first name or a company all work. The answer gives total, page and more, which is true while further pages remain.
Inputs: page, search, status.
open_signature_padOpen the signature padARead-onlyInspect
Shows a pad in the chat where the user draws their own signature or initials with a mouse or finger and saves it to Docflare. Use it when edit_document says the user has no saved signature or initials, or when they want to draw a new one. Once the pad says it is saved, place or fill the field with value saved.
Inputs: type (required).
open_upload_padOpen the upload padARead-onlyInspect
Shows a box in the chat where the user drops a PDF or a Word file (.docx), or picks one from their device, and Docflare makes it a draft the way upload_document does. Use it when sending the file to the upload_document link is blocked, for example with HTTP 403, or when the user has no file in the chat. Ask the user to drop the file there and reply once it is uploaded. The pad then gives you the new document id; without it, the newest draft in document_status is the one. Read its text and lines with get_document, then carry on with prepare_document and edit_document.
Inputs: flow.
prepare_documentPrepare a documentADestructiveIdempotentInspect
Manages who gets a draft and how it is sent: its name, who signs it and who gets a copy, by email (people new to Docflare are added to the recipients), and delivery, email, signing order, expiry, reminders and what recipients may download. Only what is sent changes; everything left out stays as it is, and settings never set take the workspace defaults. It covers any of these changes, such as "make it expire in 7 days". More signers or CCs than the plan allows are refused, naming the emails that do not fit, and nothing changes. It places no fields: a signer needs at least one, such as a signature, which edit_document places, and edit_document also sets whether signers share one copy or each get their own. On a document the user signs themselves (signed_by_sender), everyone listed gets the signed copy by email, and only the name, subject and message apply. flow switches a draft between the two, starting fresh with no recipients or fields: when the user wants to sign a signature request themselves, or have others sign a document meant for them. Nothing is sent. The answer is a preview of exactly what send_document would send, text_changes included, a preview_url that shows the pages as a signer will see them, and a review_token for send_document when nothing blocks the send.
Inputs: id (required), flow, name, message, +11 more.
save_signatureSave a drawn signatureAIdempotentInspect
Saves what the user drew on the signature pad as their signature or initials, replacing the one saved before. Only the signature pad calls this.
Inputs: type (required), image (required).
send_documentSend a documentADestructiveInspect
Sends a prepared document to its recipients. This cannot be undone. It takes the review_token of the latest preview, from prepare_document or edit_document, once the user has confirmed that preview, and the email of every signer and CC that preview lists, and sends exactly what it showed. A document the user signs themselves (signed_by_sender) is signed with the user's signature as the preview shows it and goes to its recipients at once as the signed copy. It refuses when those emails are not exactly the document's recipients, when the document changed since, naming what changed, or when the preview is older than 10 minutes. When a send fails or gets no answer, try the same review_token again: it stays valid until a send goes through, and a document is never sent twice. With link delivery, the answer gives each signer's signing link to share. When everyone has signed, Docflare emails the user, and document_status shows the progress.
Inputs: id (required), recipients (required), review_token (required).
upload_documentUpload a documentAInspect
Creates a draft document from a PDF or a Word file (.docx) in the current Docflare workspace. The file comes from one the user attached in the chat (file), from a public https link (url), or, with neither, through a one-time upload link in the answer that takes the file as a multipart POST field named file, once, for 10 minutes; when sending the file there is blocked, or the user has no file in the chat, open_upload_pad lets them drop the file into the chat instead. Docflare checks the file the way a web upload is checked, and turns a Word file into a PDF. The answer is the new draft, the text already on its pages with ids, and its lines: the blank lines where a field can sit, each with an id, its page, its position as a share of the page width and height, and the text beside it. Who gets the draft is set with prepare_document, and fields go on with edit_document. With flow sign-document the user signs the document themselves: every field is theirs, and the people added with prepare_document get the signed copy.
Inputs: url, file, flow, name.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs117 npm46 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.169 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.