record_route_outcome — neurogenesis MCP Tool
record_route_outcome
(record route outcome) is one of 14 tools on the
neurogenesis
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call record_route_outcome from your client
- Claude Code neurogenesis record_route_outcome run in your project directory
- Claude Desktop neurogenesis record_route_outcome ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor neurogenesis record_route_outcome ~/.cursor/mcp.json
- VS Code neurogenesis record_route_outcome .vscode/mcp.json
- Zed neurogenesis record_route_outcome ~/.config/zed/settings.json
- Windsurf neurogenesis record_route_outcome ~/.codeium/windsurf/mcp_config.json
- Cline neurogenesis record_route_outcome ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI neurogenesis record_route_outcome ~/.gemini/settings.json
- Grok neurogenesis record_route_outcome .mcp.json (in your project root)
- ChatGPT neurogenesis record_route_outcome Settings → Connectors → Advanced → Developer mode
- Claude.ai neurogenesis record_route_outcome Settings → Connectors → Add custom connector
- LangChain neurogenesis record_route_outcome pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http neurogenesis https://mcp.viridisconservation.com/neurogenesis/mcpOther tools on this server
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.