---
title: "How MCP Access Works with Teams, Accounts, and Permissions"
description: "How your AdLabs permissions, Teams, and API keys carry over to MCP connections."
url: https://help.adlabs.app/en/articles/93-how-mcp-access-works-with-teams-accounts-and-permissions
collection: "AdLabs MCP"
updated: 2026-11-20
language: en
---

# How MCP Access Works with Teams, Accounts, and Permissions

How your AdLabs permissions, Teams, and API keys carry over to MCP connections.

## Your MCP Connection Mirrors Your AdLabs Account

When you connect to AdLabs through MCP, you see the same Teams and profiles you have access to in the AdLabs dashboard, but you can only read data or make changes in Teams whose plan includes MCP access (Pro plans). Teams on other plans may still be listed, and requests for their data are refused.

This applies to both OAuth connections (like Claude's connector) and API key connections.

More details in the article below.

[

What the AdLabs MCP Can Access

A breakdown of what data the MCP can read, what actions it can take, and how to control permissions.

](https://help.adlabs.app/en/articles/99-what-the-adlabs-mcp-can-access.md)

## Can I Connect Multiple AdLabs Accounts at the Same Time?

Not currently. A single MCP connection is scoped to one AdLabs account.

You can't merge or combine access across different logins.

If you manage more than one account (for example, two separate brands under different logins), you'll need to log out and re-authenticate to switch between them.

## How Do API Keys Work Across a Team?

Each user in your organization gets their own API key. One key per user, not one key per organization.

If you have 5 people on your team, you can have 5 separate MCP connections, each tied to a different user.

To generate your key, go to AI > MCP and then “Manage API Key”.

[https://dashboard.adlabs.app/ai/mcp](https://dashboard.adlabs.app/ai/mcp)

![](https://staticfiles.gleap.io/p650171beb674b8f8c8958bd2/SBweik0ZDkhV0EEdrco0mnudNYHV6HvIXikWKN2UXJetro1c3IoOUeYTpE0OMdBb05TiW7uvXXO.png)

![](https://staticfiles.gleap.io/ghelparticle/mnMKTj0U6DfQhSVCAk1E1WQglz0DdaBWNh0jxzC6pIecIKhTGKkTM2VImYvYdHireBJvHUUj69x.png)

API keys are user-specific. Every action taken through an API key is tracked to the user who generated it, so you can see exactly who made what changes.

> **Error:** **Heads up:** If you rotate or disable your API key, any MCP connections using that key will immediately lose access. You'll need to update your MCP configuration with the new key.

## Can I Create a Read-Only API Key?

Not currently.

All API keys have the same access level as the user who generated them, including their role on each Team. To make someone's MCP access read-only, give them the “Viewer” role on the Team: by default a Viewer can read data through MCP but can't make changes, unless a Team owner or admin has turned on extra permissions for Viewers. To limit which profiles they can see, use Teams to scope their account access to specific profiles (see below).

## Giving a Client MCP Access Without Exposing Your Full Account

If you're an agency and want to give a client access to their data through MCP without exposing other accounts you manage:

1.  Create a new Team in AdLabs for that client
    
2.  Add only the profiles relevant to that client
    
3.  Invite the client to that Team
    

When the client connects via MCP, they'll only see what's in the Team you added them to. They won't have visibility into your other Teams, profiles, or clients.

[

What Are AdLabs "Teams"?

How do Teams work in AdLabs?

](https://help.adlabs.app/en/articles/71-what-are-adlabs-teams.md)

## Why Can't I See Certain Profiles in MCP?

MCP respects the same access controls as the AdLabs UI. If a profile isn't showing up, check whether you have access to it in the dashboard first, and that the Team it belongs to is on a plan that includes MCP access.

If you can see it in the UI but not through MCP, please ask your AI assistant to submit a bug ticket. That will go directly to our software team.
