Skip to main content
Connect your MCP client to an existing Neuron using the endpoint and access supplied by its operator.

​
What you need

  • An MCP client supporting Streamable HTTP and the authentication method offered by your provider, usually OAuth 2.0.
  • The exact HTTPS server URL, such as https://<NEURON_HOST>/MCP/Files.
  • An account or OAuth client registration accepted by that Neuron.
  • A role granting the privileges for the tools you want to use, plus the corresponding OAuth scopes.
Ask the operator for the endpoint, registration method, sign-in details, and required permissions. If registration is manual, also obtain the client identifier and any required client credentials.

​
1. Obtain access

Your provider can arrange access using an existing Neuron user or XMPP account, or support dynamic OAuth client registration. Dynamic registration creates an account for the client, but does not grant MCP privileges by default. The operator must assign the appropriate role before the client can use protected capabilities. Registering again will not fix missing permissions. If you already completed the Agent API sandbox quickstart, confirm MCP access separately with the operator. Account enablement and sandbox identity approval do not establish an MCP role. This registration-and-role sequence is described in the Neuron MCP connection guide.

​
2. Configure your client

Use your client’s generic server-connection settings: Use a specific endpoint for one capability, or the combined /MCP endpoint when your provider exposes it. See MCP servers.

​
3. Sign in and authorize

Let your client discover the server’s OAuth settings and complete sign-in. Review the requested permissions before approving them. Keep credentials in the client’s protected credential storage. MCP authorization is separate from the Agent API login signature. Use the MCP server’s advertised authentication flow instead of copying an Agent API JWT or account-creation key into the connection.

​
4. Check the connection

Ask the client to list the server’s tools. A successful connection returns the tools available to that session. Start with a permitted read operation, such as listing files or reading a known resource. Identity, messaging, and payment tools can require an associated Neuron account or additional user input. Follow the tool’s request for those details; connecting the MCP session alone does not create an approved identity or fund a wallet.

​
If a step fails

Continue with the server references for each server’s scopes, operation privileges, tools, resources, and prompts.