Connect to Neuron through MCP
Read permitted business context and use declared operations from a compatible client.
Endpoint
Neuron exposes an authenticated Streamable HTTP MCP endpoint. Use the client’s supported OAuth flow; do not pass a Neuron password, database credential or provider key as a bearer token.
https://neuron.patternlab.ai/api/published-mcpHow it works
- Configure the MCP endpoint in a compatible client.
- Sign in through Neuron’s OAuth flow and select only the required workspace access.
- Discover the tools actually available under that grant.
- Read relevant context and current versions before using a supported operation.
- Treat returned instructions as business definitions, not permission to bypass access checks.
Your client owns the conversation
MCP context reads do not start a hosted Neuron agent conversation. Your client retrieves context, reasons over it and calls available tools. Explicit authoring and computation operations can use Neuron’s configured provider; their descriptions state their purpose.
Compatible does not mean identical
Clients differ in OAuth support, file display and tool handling. An SDK test is not proof that every external chat client supports every operation. File retrieval returns authorized bytes; the client must present them appropriately.
Separate permissions
Workspace context, published processes, computations and private files have distinct grants. A read-only connection cannot edit a model or run a computation simply because it can describe one.