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