---
title: "Connect AI assistants through MCP and reuse token scopes"
description: "Enable MCP on a Core API token and manage reusable scopes across integrations."
type: changelog
date: "2026-10-30"
changelog:
  category: API
---

Brella's [MCP server](https://docs.brella.io/agents/mcp) is now available at `/api/mcp`. Connect a compatible remote HTTP MCP client with a Core API token to discover tools for the resources and actions its scopes allow.

- Turn on **Enable MCP use** for the token. MCP is off by default, and turning it off leaves direct Core API access unchanged.
- MCP uses bearer-token authentication and the same organization, event boundaries, field selections and write rules as the Core API.
- Manage reusable scopes in **API → Scopes**, then assign them through a token's **Associated scopes** tab or a scope's **Associated tokens** tab. Each token can hold one scope per resource.
- Scope access-level presets provide a starting selection. **Read only** selects all readable fields, filters and related data; review and narrow these before saving. **Read + write** adds supported non-delete actions. Delete is always a separate choice.

Existing direct Core API clients keep their current authentication header and permissions. Scope edits now apply to every associated token. Deleting a token removes its associations while preserving the scope definitions and other tokens.

See [Configure token scopes](https://docs.brella.io/getting-started/token-scopes) for the updated Admin Panel workflow and [Connect through MCP](https://docs.brella.io/agents/mcp) for connection details, tool arguments and troubleshooting.