> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to a local Neuron

> Prepare a Neuron you administer for local MCP development

“Local” means you administer the Neuron. Codex may run on the same machine or elsewhere; the OAuth and permission model is the same.

## 1. Confirm the Neuron is ready

Complete [installation](/operations/install) and [first run](/operations/first-run). Then confirm the target endpoint responds over HTTPS:

```bash theme={null}
curl -i https://<NEURON_HOST>/MCP/Files
```

An authentication response is expected. A `404` means the endpoint or module is unavailable.

## 2. Add a read-only role

Open **Administration → Users and Roles → Roles** and create a role with:

```text theme={null}
OAUTH.Scope.MCP.Files.Resources.List
OAUTH.Scope.MCP.Files.Resources.Read
OAUTH.Scope.MCP.Files.Tools.Search
```

Assign it to the account you will use during OAuth login.

## 3. Make client registration available

Choose one path:

* Use a static OAuth client already provisioned for Codex by the distribution or deployment tooling.
* Enable and test dynamic client registration for your deployment.

The Neuron's OAuth metadata must be reachable at:

```bash theme={null}
curl --fail https://<NEURON_HOST>/.well-known/oauth-authorization-server
```

If your installation does not provide either client-registration path, MCP login is not ready. The current public administration surface does not provide a universal manual-client workflow, and generating a token by hand is not the missing setup step.

## 4. Connect Codex

Continue with [Connect Codex](/mcp/quickstart), using your actual host and registration method.

<Tip>
  Begin with `/MCP/Files` and read-only scopes. Add write or destructive privileges only after read access works and you have tested which resources the account can reach.
</Tip>