scan_document — mcp MCP Tool
scan_document
(scan document) is one of 3 tools on the
mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scan_document from your client
- Claude Code mcp scan_document run in your project directory
- Claude Desktop mcp scan_document ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp scan_document ~/.cursor/mcp.json
- VS Code mcp scan_document .vscode/mcp.json
- Zed mcp scan_document ~/.config/zed/settings.json
- Windsurf mcp scan_document ~/.codeium/windsurf/mcp_config.json
- Cline mcp scan_document ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp scan_document ~/.gemini/settings.json
- Grok mcp scan_document .mcp.json (in your project root)
- ChatGPT mcp scan_document Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp scan_document Settings → Connectors → Add custom connector
- LangChain mcp scan_document pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.doc.cheap/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.