how_to_connect — INITE Brain MCP Tool
how_to_connect
(how to connect) 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 how_to_connect from your client
- Claude Code INITE Brain how_to_connect run in your project directory
- Claude Desktop INITE Brain how_to_connect ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor INITE Brain how_to_connect ~/.cursor/mcp.json
- VS Code INITE Brain how_to_connect .vscode/mcp.json
- Zed INITE Brain how_to_connect ~/.config/zed/settings.json
- Windsurf INITE Brain how_to_connect ~/.codeium/windsurf/mcp_config.json
- Cline INITE Brain how_to_connect ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI INITE Brain how_to_connect ~/.gemini/settings.json
- Grok INITE Brain how_to_connect .mcp.json (in your project root)
- ChatGPT INITE Brain how_to_connect Settings → Connectors → Advanced → Developer mode
- Claude.ai INITE Brain how_to_connect Settings → Connectors → Add custom connector
- LangChain INITE Brain how_to_connect 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
- search_knowledge
- search_multi_hop
- graph_retrieve
- 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.