Migrating from Project Brain MCP

Neusis Neuron replaces the earlier Project Brain MCP (mcp-project-brain) server. If you have an existing Project Brain MCP setup, migrating takes a couple of minutes.

What changed

	Project Brain MCP (old)	Neusis Neuron (new)
Binary	mcp-project-brain	neusis-neuron-mcp
MCP key	project-brain	neusis-neuron
Tools	kb_config, kb_list, kb_read, kb_search, kb_write	get_file_contents, get_repository_tree, search_code
Writes	kb_write could commit to the repo	None — read-only
Token	Contents: Read and write	Contents: Read
AGENTS.md at repo root	Required (kb_config read it)	Not required

Neusis Neuron is read-only by design: there is no kb_write and no commit capability. It also drops the hand-rolled kb_* tools in favour of three standard, repo-scoped GitHub tools.

Migrate in three steps

1. Install the new server

Follow Installation to install neusis-neuron-mcp. You can leave the old mcp-project-brain binary in place; it simply won't be referenced any more.

2. Swap the config entry

In neusiscode.json, replace the old project-brain block:

{
  "mcp": {
    "project-brain": {
      "type": "local",
      "command": ["mcp-project-brain", "stdio", "--kb-repo=OWNER/REPO"],
      "environment": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_your_token" },
      "enabled": true
    }
  }
}

with the new neusis-neuron block:

{
  "mcp": {
    "neusis-neuron": {
      "type": "local",
      "command": ["neusis-neuron-mcp", "stdio", "--kb-repo", "OWNER/REPO"],
      "environment": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_your_token" },
      "enabled": true
    }
  }
}

The --kb-repo value carries over unchanged. See Configuration for the full reference.

3. Downgrade the token (optional)

Because Neusis Neuron never writes, you can regenerate the GitHub token with Contents: Read only. The previous read/write token will keep working, but read-only is the recommended least-privilege setup.

Do I need to update tool names anywhere?

Usually no. The bundled Project Brain skill that tells the agent how to use the KB references the new tool names for you. If you have your own prompts or skills that called kb_read / kb_search directly, point them at get_file_contents and search_code instead — see Tools.