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