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