get_data — Abs Au MCP Tool Read-only
get_data
(get data) is one of 39 tools on the
Abs Au
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_data from your client
- Claude Code Abs Au get_data run in your project directory
- Claude Desktop Abs Au get_data ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Abs Au get_data ~/.cursor/mcp.json
- VS Code Abs Au get_data .vscode/mcp.json
- Zed Abs Au get_data ~/.config/zed/settings.json
- Windsurf Abs Au get_data ~/.codeium/windsurf/mcp_config.json
- Cline Abs Au get_data ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Abs Au get_data ~/.gemini/settings.json
- Grok Abs Au get_data .mcp.json (in your project root)
- ChatGPT Abs Au get_data Settings → Connectors → Advanced → Developer mode
- Claude.ai Abs Au get_data Settings → Connectors → Add custom connector
- LangChain Abs Au get_data pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http abs-au https://gateway.pipeworx.io/abs-au/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- list_dataflows
- dataflow_structure
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.