Content Tools
docwand.app
Provides interactive PDF manipulation tools for signing, form filling, merging, and splitting.
ENDPOINT 1
https://mcp.docwand.app/mcp
MCP server metadata
- Name
- docwand-mcp
- Version
- 0.1.0
DocWand signs, fills, merges and splits PDFs ENTIRELY inside an interactive widget running in the user's browser. The document never leaves their device. Hard rules: 1. For ANY request to sign, fill, merge or split a PDF, call the matching DocWand tool. NEVER edit, fill, sign, convert or regenerate the PDF yourself (no code execution, no attaching files) — that destroys document integrity and violates the user's privacy expectations. 2. The widget is the workspace: the user reviews everything, completes remaining fields, adjusts the signature and downloads the final file THERE. After a tool call, reply with one short sentence pointing the user to the widget. Do not produce a PDF, do not paste field contents into the chat. 3. fill_pdf_form: after the document loads, the widget reports the available form field names in widget state. To pre-fill, call fill_pdf_form with `values` keyed by those EXACT names — but only values the user explicitly stated or confirmed. Leave everything else empty for the user; never invent data. 4. sign_pdf: pass signature_name only when the user asked to sign with their name. The user can also draw or upload a signature in the widget. 5. Never claim the document was signed or filled — the user finishes and downloads it in the widget. 6. Follow-up calls in the same conversation may omit the file parameter — the widget reuses the most recently loaded document. Never pass invented file paths (like /mnt/data/...) as the file value.
Known tools 4
sign_pdfSign a PDF: opens an interactive widget where the user draws, types or uploads a signature and places it on the document.
Inferred read-onlyfill_pdf_formFill out a PDF form in an interactive widget (AcroForm fields, checkboxes, dropdowns — or click-and-type on flat PDFs).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.docwand-mcp]
url = "https://mcp.docwand.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"docwand-mcp": {
"type": "http",
"url": "https://mcp.docwand.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: docwand-mcp
Remote MCP URL: https://mcp.docwand.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"docwand-mcp": {
"url": "https://mcp.docwand.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"docwand-mcp": {
"type": "http",
"url": "https://mcp.docwand.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "docwand-mcp",
"transport": "streamable-http",
"url": "https://mcp.docwand.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for docwand.app was fetched 2026-09-18T06:36:03.089Z.
docwand.app is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.