Connect an AI agent over MCP
Use the Agents page to connect Claude with the intended workspace scope and access mode.
Before you start
Core’s Agents page provides connection values and client instructions for Model Context Protocol (MCP). The steps below follow the instructions shown there for claude.ai, Claude Desktop, and Claude Code over HTTP.
- Sign in to Core and select the intended workspace. Being signed in alone does not grant permission to query it.
- Check that the workspace is available to agents for your account. If the page says it is unavailable, ask an organization admin about your access.
- The workspace needs a working database connector to answer data questions. Access to a workspace and database readiness are separate checks; a workspace listed as reachable may still need database setup.
- Use the same DataBrill account when the client opens the DataBrill sign-in page. A different login connects that account’s workspaces instead.
Choose the scope and mode
- Open Workspace → Agents.
- Under MCP scope, choose the narrowest scope that suits the task: Workspace, Organization, or User. Check Workspaces this connection can reach before proceeding.
- Leave Read-only on for questions and analysis. Changing scope starts in read-only mode again.
- Select your Client and use the Connector URL, OAuth client ID, or command generated on your own page. Do not substitute another account’s values.
Workspace scope addresses the selected workspace. Organization scope reaches the workspaces you are allowed to query within the organization that owns that workspace. User scope reaches the workspaces you are allowed to query across organizations. Neither wider scope grants access to a workspace you could not otherwise query.
With Organization or User scope, one question still reaches one workspace: the agent uses listWorkspaces, then passes that workspace’s wsid with its question.
The URL narrows what this connector does; it grants no new access. Your DataBrill credential remains account-wide, and running connectors for two scopes at once does not isolate their credentials. Read-only and write mode are also choices for the connector, not restrictions you can impose on another person who holds the login.
Connect claude.ai
- In claude.ai, open Settings → Connectors and choose to add a custom connector.
- Paste the Connector URL from your Core Agents page.
- Open the connector’s advanced OAuth settings and enter the OAuth client ID from that page. Leave the client secret empty.
- Choose Connect, then sign in on the DataBrill login page with the same account you used in Core.
Connect Claude Desktop
- Open Settings → Connectors and choose to add a custom connector.
- In that dialog, paste the Connector URL and enter the OAuth client ID from your Core Agents page. Leave the client secret empty.
- Choose Connect and sign in to DataBrill with the same account you used in Core.
Connect Claude Code over HTTP
Run both commands in a real terminal. The Authenticate prompt does not appear in an IDE extension’s panel.
- Select Claude Code on the Core Agents page. Copy and run its generated add-server command. It includes your selected connector URL, access mode, and client ID.
- Run
claude /mcp, choosedatabrill-core, then choose Authenticate. - Sign in on the DataBrill login page with the same account you used in Core, then return to the terminal for the connection confirmation.
Check the result
After the client confirms the connection, ask a simple question such as “Which tables are available in this workspace?” For a wider scope, identify the intended workspace before asking about its data.
A successful connection and a successful data question are separate checks. If sign-in succeeds but a question fails, check which account signed in, the selected scope, the reachable workspace list, and whether that workspace has a working database connector.
Limits of write access
With Read-only on, the agent runs queries and returns answers; it cannot change data. Turning it off allows adding, changing, and removing rows only in configuration tables named brand_config_*. There is no undo.
Imported reports, orders, and advertising data stay unwritable. Neither mode can change DataBrill account settings, connectors, or people. Scope and mode only narrow capabilities your login already holds.
When to contact support
These instructions cover the three client procedures shown in Core, not every MCP client or client subscription. Client menus can change. Use the current generated values and instructions on Agents rather than a copied example URL.
Ask an organization admin when the workspace is unavailable to agents for your account. Contact support about a missing database connector, failed queries, repeated sign-in failures, or a client procedure that no longer matches its interface. Include the client name, chosen scope and mode, workspace name, and sanitized error message. Never send passwords, access tokens, or client secrets.