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