pdf_text_extract — ToolSnap MCP MCP Tool
pdf_text_extract
(pdf text extract) is one of 17 tools on the
ToolSnap MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call pdf_text_extract from your client
- Claude Code ToolSnap MCP pdf_text_extract run in your project directory
- Claude Desktop ToolSnap MCP pdf_text_extract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ToolSnap MCP pdf_text_extract ~/.cursor/mcp.json
- VS Code ToolSnap MCP pdf_text_extract .vscode/mcp.json
- Zed ToolSnap MCP pdf_text_extract ~/.config/zed/settings.json
- Windsurf ToolSnap MCP pdf_text_extract ~/.codeium/windsurf/mcp_config.json
- Cline ToolSnap MCP pdf_text_extract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ToolSnap MCP pdf_text_extract ~/.gemini/settings.json
- Grok ToolSnap MCP pdf_text_extract .mcp.json (in your project root)
- ChatGPT ToolSnap MCP pdf_text_extract Settings → Connectors → Advanced → Developer mode
- Claude.ai ToolSnap MCP pdf_text_extract Settings → Connectors → Add custom connector
- LangChain ToolSnap MCP pdf_text_extract pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http toolsnap-mcp https://mcp.toolsnap.app/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.