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