Skip to main content
Model Context Protocol (MCP) lets an AI client call tools and read resources exposed by a Neuron. You connect to one capability at a time and sign in through the Neuron’s OAuth service.
MCP servers differ by deployment. Ask the Neuron operator for the endpoint, OAuth client settings, required role, and list of enabled tools.

Connect Codex

Add a Neuron endpoint, sign in, and make a first read-only request.

​
Common MCP endpoints

There is no documented combined /MCP endpoint. A package can add other endpoints, so use the exact URL supplied by the Neuron operator.

​
What you need

You do not need the Neuron source code. You need:
  • a reachable Neuron URL;
  • an MCP endpoint;
  • an OAuth client ID, or confirmation that dynamic client registration is enabled;
  • an account or sign-in flow with the required role.
For a Neuron running on your machine, you configure access yourself. For another Neuron, its operator provides these values and grants access.

​
Choose another tool when

The listed servers do not create or install Neuron packages, author contracts, or issue tokens. Use the package tools, LegalLab, or Agent API for those tasks.

Local Neuron

Configure access when you administer the Neuron.

Remote Neuron

Connect using values supplied by its operator.

Built-in servers

Choose an endpoint and review its permissions.

Build a server

Add MCP tools from a C# package.