resolve_entity — Brave Search MCP Tool Read-only
resolve_entity
(resolve entity) is one of 38 tools on the
Brave Search
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolve_entity from your client
- Claude Code Brave Search resolve_entity run in your project directory
- Claude Desktop Brave Search resolve_entity ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Brave Search resolve_entity ~/.cursor/mcp.json
- VS Code Brave Search resolve_entity .vscode/mcp.json
- Zed Brave Search resolve_entity ~/.config/zed/settings.json
- Windsurf Brave Search resolve_entity ~/.codeium/windsurf/mcp_config.json
- Cline Brave Search resolve_entity ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Brave Search resolve_entity ~/.gemini/settings.json
- Grok Brave Search resolve_entity .mcp.json (in your project root)
- ChatGPT Brave Search resolve_entity Settings → Connectors → Advanced → Developer mode
- Claude.ai Brave Search resolve_entity Settings → Connectors → Add custom connector
- LangChain Brave Search resolve_entity pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http brave-search https://gateway.pipeworx.io/brave-search/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- 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
- web_search
- news_search
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.