Connect an AI assistant

Nucleo runs one remote Model Context Protocol server at https://mcp.nucleoplatform.com. An AI client connected to it sees the tools of every Nucleo module the person can use — Brain, Catalog, Commerce, Intelligence — in the company they choose, with their own roles and permissions. No tool deletes data.

There are no keys to copy: the person signs in to Nucleo from the AI client and approves a consent screen. The client gets an OAuth access token that only works on the AI tools.

Claude (web, desktop and mobile apps):

1. In Claude, go to Settings > Connectors and select Add custom connector.
2. Name it Nucleo and enter the URL https://mcp.nucleoplatform.com.
3. Select Connect, sign in to Nucleo and approve access.

ChatGPT (developer mode):

1. In ChatGPT, go to Settings > Connectors > Advanced and turn on developer mode.
2. Select Create, enter the MCP server URL https://mcp.nucleoplatform.com and choose OAuth authentication.
3. Sign in to Nucleo and approve access.

If the person belongs to more than one company, the assistant can list them and switch with the connector's own tools before working.

Any MCP client that supports remote servers with OAuth works. The server speaks protocol version 2025-06-18 over Streamable HTTP with JSON responses (no server-sent stream). The flow your client runs:

1. POST https://mcp.nucleoplatform.com without a token → 401 with a WWW-Authenticate header pointing to the protected-resource metadata (RFC 9728).
2. The metadata names https://auth.nucleoplatform.com as authorization server; read its metadata at /.well-known/oauth-authorization-server.
3. Register the client at /oauth/register (RFC 7591) with your redirect_uris.
4. Run the authorization code flow with PKCE (S256); the person signs in and consents.
5. Exchange the code at /oauth/token, then send Authorization: Bearer <token> on every MCP request. Refresh with the refresh token when it expires.

curl -X POST https://auth.nucleoplatform.com/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Acme Ops Assistant",
    "redirect_uris": ["https://assistant.acme.example/oauth/callback"],
    "token_endpoint_auth_method": "none"
  }'

curl -X POST https://mcp.nucleoplatform.com \
  -H "Authorization: Bearer $NUCLEO_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

Every call to /oauth/register creates a new client: register once and store the client_id. Redirect URIs must be https, except loopback addresses for local tools.

If you run your own agent runtime and do not need MCP, the same tools are available as plain HTTP on each module: GET /api/v1/ai-tools lists them with their JSON Schema, POST /api/v1/ai-tools/{name} runs one. Use the same OAuth token and name the company in X-Nucleo-Company. See AI Tools.

• The assistant can do only what the person can do in Nucleo, in the active company.
• Commerce and Intelligence tools are read-only. Brain and Catalog have write tools, marked as such in the tool list.
• Catalog applies only small, reversible changes from an AI client. Larger ones — bulk changes, publishing, imports, deletions — come back as a preview and the person confirms them inside Nucleo.
• Tokens issued to AI clients work only on the AI tools: they cannot call any other Nucleo API.
• To disconnect, remove the connector in the AI client; the token can also be revoked with POST https://auth.nucleoplatform.com/api/auth/revoke.