doc_read — McpStamp Word Documents MCP Tool
doc_read
(doc read) is one of 14 tools on the
McpStamp Word Documents
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call doc_read from your client
- Claude Code McpStamp Word Documents doc_read run in your project directory
- Claude Desktop McpStamp Word Documents doc_read ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor McpStamp Word Documents doc_read ~/.cursor/mcp.json
- VS Code McpStamp Word Documents doc_read .vscode/mcp.json
- Zed McpStamp Word Documents doc_read ~/.config/zed/settings.json
- Windsurf McpStamp Word Documents doc_read ~/.codeium/windsurf/mcp_config.json
- Cline McpStamp Word Documents doc_read ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI McpStamp Word Documents doc_read ~/.gemini/settings.json
- Grok McpStamp Word Documents doc_read .mcp.json (in your project root)
- ChatGPT McpStamp Word Documents doc_read Settings → Connectors → Advanced → Developer mode
- Claude.ai McpStamp Word Documents doc_read Settings → Connectors → Add custom connector
- LangChain McpStamp Word Documents doc_read pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http docx-document-generator-proposal-contract-markdown https://mcp.zovo.one/mcp/docxOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.