
neurogenesis
Developmental agents for the agent economy: create an agent from a digital genome, then evolve it wi
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Developmental agents for the agent economy: create an agent from a digital genome, then evolve it wi
How to connect
How to connect neurogenesis to Claude
The server address to paste into Claude settings:
https://mcp.viridisconservation.com/neurogenesis/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect neurogenesis to ChatGPT
The server address to paste into ChatGPT settings:
https://mcp.viridisconservation.com/neurogenesis/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect neurogenesis to Cursor
The server address to paste into Cursor settings:
https://mcp.viridisconservation.com/neurogenesis/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (14)
Raw names from tools/list. Only developers need these.
| create_agent | Create a developmental agent from a digital genome: {agent_name, purpose, initial_nodes (unique, >=1), fitness_metrics (>=1), optional growth_rules / safety_axioms}. Returns agent_id + initial graph summary. |
| submit_evaluation | Evolve an agent with one task outcome: {task_id, task_type, success_score in [0,1], optional accuracy/user_satisfaction/ cost_efficiency/safety_score/notes/used_nodes/used_edges}. Success strengthens the used edges, failure weakens them; growth and pruning follow the genome's rules under its safety axioms (NG1). Returns the new developmental-ledger events. |
| get_agent | Full current state: genome, cognitive graph (nodes/edges with weights and trust), and summary counts. |
| list_agents | All developmental agents on this mount, with summary counts. |
| best_next_steps | Routing recommendation: the strongest next cognitive steps from a given node, by learned edge weight and trust. |
| get_ledger | The append-only developmental ledger: every growth, pruning, and evaluation event with reasons (NG3 — returned verbatim). |
| export_state | Portable state document for an agent (import_state recreates it anywhere — including a self-hosted verdigraph-neurogenesis). |
| import_state | Recreate an agent from an export_state document. |
| delete_agent | Remove a developmental agent from this mount. |
| register_compute_profile | Register a caller-owned Wu Wei execution profile: reuse/cache, deterministic rule, local model, tool/workflow, or cloud model. Profiles can declare quality, reliability, capabilities, token costs, latency, locality, energy rates or average power, carbon intensity, and cache confidence/age. Routing never invents capacity or energy evidence. |
| route_task | Choose the least-burden eligible route for a task. Hard constraints include quality, reliability, locality, capabilities, context, cost, latency, and energy. Optional baselines quantify predicted savings. Explicit allow_defer/value/urgency fields may produce a no-work decision; no result is then claimed. Returns a hash-bound decision receipt. |
| record_route_outcome | Attach one observed outcome to a Wu Wei decision. Actual cost, latency, and energy are optional and remain explicitly unknown when omitted. One append-only, hash-bound outcome is allowed per decision. |
| compute_efficiency_report | Free read: decision/outcome receipts, route modes, compute avoided, predicted savings, predicted-vs-observed cost/latency/energy coverage, and Landauer-floor context. Estimates and observations stay distinct. |
| describe_agent | Return capabilities and input contract. |