Vespper MCP
The docx MCP for agents
Give your AI agents tools to create, read, and edit Word documents. Connect once via MCP — your agent handles .docx from there.
Setup
Add the server to your MCP config, set VESPPER_API_KEY to your key, and restart your client.
mcp.json
{
"mcpServers": {
"vespper-docx-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.vespper.com/mcp",
"--header",
"Authorization:Bearer $VESPPER_API_KEY"
]
}
}
}Endpoint: https://mcp.vespper.com/mcp · Transport: MCP over HTTP via mcp-remote
What you can do
Create .docx filesGenerate Word documents from structured content. Your agent drafts the doc; Vespper returns a properly formatted .docx.
Read & extractPull text, structure, and metadata from existing Word files so your agent can reason over document content.
Edit in placeApply revisions to .docx files — insert paragraphs, update sections, and preserve formatting and styles.
Works everywhereStandard MCP over HTTP. Connect from Cursor, Claude Desktop, Windsurf, Cline, or any client that supports MCP remote servers.
Bearer authAuthenticate with a Vespper key. Pass it as an Authorization header — no OAuth dance required for local agent setups.
Built for agentsTools designed for LLM workflows: clear inputs, structured outputs, and .docx files your agent can pass to the next step.
Common use cases
Draft compliance reports and export to Word from a coding agent
Read an incoming contract .docx and extract clauses for review
Update a document library when templates or regulations change
Generate tracked-change revisions before human sign-off
Pipe agent output directly into your team's existing .docx workflows
Ready to connect?Sign up, grab a key, and add Vespper to your MCP config.
Get started free
Contact
founders@vespper.com