NeuroStack MCP Server

What the code does

We read the source, 16 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

postinstall: node postinstall.js

    const result = execSync(lookup, { encoding: "utf8", stdio: ["pipe", "pipe", "pipe"] }).trim();

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        result = subprocess.run(

                    cfg.checkpoint_command, shell=True, input=prompt.text,

    for path in sorted(root.rglob(filename)):

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

claude mcp add neurostack --transport http https://mcp.neurostack.sh/mcp

{
  "mcpServers": {
    "neurostack": {
      "url": "https://mcp.neurostack.sh/mcp"
    }
  }
}

[mcp_servers.neurostack]
url = "https://mcp.neurostack.sh/mcp"

{
  "mcpServers": {
    "neurostack": {
      "url": "https://mcp.neurostack.sh/mcp"
    }
  }
}

{
  "mcpServers": {
    "neurostack": {
      "url": "https://mcp.neurostack.sh/mcp"
    }
  }
}

This one needs environment variables set before it will start: NEUROSTACK_VAULT_ROOT (Path to your Markdown vault (e.g. ~/brain, ~/notes)). The author declared them in the registry entry; get the values from the project itself.

Endpoints