Skip to main content
A Neuron can publish the following MCP endpoints. Confirm which ones your provider enables, then use your client’s tool discovery to see the available operations. Prefix each path with your Neuron’s HTTPS host, for example https://<NEURON_HOST>/MCP/Identity. Use the combined endpoint for one connection to available capabilities, or an individual endpoint for a smaller tool set. Each server page lists its scopes, required privileges, tools, resources, and prompts, with links to complete operation arguments in the original MCP documentation.

​
Requirements by capability

All protected operations require the role and permissions described in Scopes and permissions. A combined connection does not grant additional permissions.
  • Messaging: an account the MCP server can connect on your behalf.
  • Identity and contracts: account access, identity approval where required, and the parties, roles, and templates needed by the contract.
  • Payments: a connected account and Legal Identity, plus the balance or payment-provider setup needed for the operation.
The MCP server manages the underlying protocol connection. Your application uses MCP tools to perform these tasks. For the objects and lifecycle behind the tools, see Legal Identities, contracts, and wallets and payments.