graph_retrieve — INITE Brain MCP Tool
graph_retrieve
(graph retrieve) is one of 30 tools on the
INITE Brain
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call graph_retrieve from your client
- Claude Code INITE Brain graph_retrieve run in your project directory
- Claude Desktop INITE Brain graph_retrieve ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor INITE Brain graph_retrieve ~/.cursor/mcp.json
- VS Code INITE Brain graph_retrieve .vscode/mcp.json
- Zed INITE Brain graph_retrieve ~/.config/zed/settings.json
- Windsurf INITE Brain graph_retrieve ~/.codeium/windsurf/mcp_config.json
- Cline INITE Brain graph_retrieve ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI INITE Brain graph_retrieve ~/.gemini/settings.json
- Grok INITE Brain graph_retrieve .mcp.json (in your project root)
- ChatGPT INITE Brain graph_retrieve Settings → Connectors → Advanced → Developer mode
- Claude.ai INITE Brain graph_retrieve Settings → Connectors → Add custom connector
- LangChain INITE Brain graph_retrieve pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http inite-brain-service https://brain.inite.ai/mcp
Other tools on this server
- about_brain
- how_to_connect
- search_knowledge
- search_multi_hop
- synthesize
- memory_diff
- get_entity_profile
- get_entity_timeline
- summarize_entity
- get_competing_facts
- detect_contradiction
- get_fact
- get_fact_provenance
- find_related_entities
- match_procedure
- list_procedures
- search_communities
- list_communities
- find_entity_communities
- why
- recall_decisions
- get_source_reputation
- workspace_status
- record_fact
- link_entities
- retract_fact
- record_procedure
- retire_procedure
- record_decision
This list was read from the server itself, by connecting to it and calling tools/list on 4 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.