list_procedures — INITE Brain MCP Tool Read-only
list_procedures
(list procedures) 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 list_procedures from your client
- Claude Code INITE Brain list_procedures run in your project directory
- Claude Desktop INITE Brain list_procedures ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor INITE Brain list_procedures ~/.cursor/mcp.json
- VS Code INITE Brain list_procedures .vscode/mcp.json
- Zed INITE Brain list_procedures ~/.config/zed/settings.json
- Windsurf INITE Brain list_procedures ~/.codeium/windsurf/mcp_config.json
- Cline INITE Brain list_procedures ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI INITE Brain list_procedures ~/.gemini/settings.json
- Grok INITE Brain list_procedures .mcp.json (in your project root)
- ChatGPT INITE Brain list_procedures Settings → Connectors → Advanced → Developer mode
- Claude.ai INITE Brain list_procedures Settings → Connectors → Add custom connector
- LangChain INITE Brain list_procedures pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http inite-brain-service https://brain.inite.ai/mcpOther 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
- match_procedure
- 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.