Do I need a manager account for a developer token?

Yes. The token is issued through a manager (MCC) account's API Center. Ordinary Google Ads accounts don't expose it, even if you only ever manage one ad account.

What can I do with a test developer token?

Only reach test accounts, which never serve real ads or spend money. It's ideal for building and validating an integration, but you need Basic or Standard access to touch live accounts.

How long does Basic access approval take?

It varies, but often a few business days. Google reviews applications manually against its Required Minimum Functionality policy, and incomplete or non-compliant submissions get rejected.

How to Get a Google Ads Developer Token for MCP Access

VigilDog Team · October 17, 2026 · 6 min read

Every call to the Google Ads API carries a developer token in its request header. It gates how much of the API you're allowed to use, and it's the first wall people hit when they try to drive Google Ads from an MCP. Getting a Google Ads developer token is straightforward once you know where it lives and which access level you actually need.

What a developer token is, and isn't

Because an Ads MCP server is just a Google Ads API client wearing a friendlier interface, no token means no access, the MCP can authenticate a user all day and still get rejected at the door. The token identifies your application to Google, not the user.

It's easy to confuse the developer token with OAuth credentials, but they do different jobs. OAuth (a client ID, secret, and refresh token) proves which user is acting and which accounts they can touch. The developer token proves which application is calling and at what tier. You need both. The token also comes in access levels, Test, Basic, and Standard, and the level you hold decides which accounts you can reach at all.

Step 1: create a manager (MCC) account

The developer token is not issued from an ordinary Google Ads account. It lives in the API Center, which only manager accounts (MCC) expose. If you don't already manage accounts under an MCC, create one through the Google Ads manager signup, it's free and takes a few minutes.

This manager account becomes the home of your token and, later, the login-customer-id that your API calls reference. Even if you only run a single ad account, you'll still create a manager account on top of it to obtain the token.

Step 2: apply in the API Center

Signed into the manager account, open Admin then API Center (in older interfaces, Tools & Settings then Setup then API Center). You'll complete a short application describing your company and intended use, and accept the Google Ads API Terms. On submission you're issued a token immediately, but at Test access only.

Test access is deliberately limited: your token can call the API, but only against test accounts, accounts explicitly flagged as test, which never serve real ads or spend money. This is the correct place to build and validate an MCP integration end to end before a single live dollar is at risk.

Step 3: apply for Basic or Standard access

To touch real, spending accounts you must upgrade to Basic access. From the API Center you submit an application form describing your tool: what it does, who uses it, and, critically, how it complies with Google's Required Minimum Functionality (RMF) policy. Google reviews it manually; approvals commonly take a few business days, and vague or non-compliant applications get bounced.

Basic access grants a daily operations quota that's enough for most agencies and internal tools. Standard access raises those limits and is applied for later, once you have real usage to point to. For running a handful of ad accounts from an assistant, Basic is the tier you're aiming for, just plan for the review time, because it's the step people forget until launch day.

Test access, issued instantly, works only against test accounts
Basic access, requires manual approval, unlocks live accounts with a daily quota
Standard access, higher limits, applied for later once you have usage history

How the token fits an MCP setup

Once approved, a single request from your MCP carries three things together: the developer token (your app tier), an OAuth access token derived from the user's refresh token (who is acting), and a login-customer-id header set to your manager account (the context for the call). The assistant proposes an action, the MCP validates and executes it against the Google Ads API, and results flow back.

Treat the token like a password: it belongs in an environment variable or secret store, never hardcoded or committed. If you'd rather not assemble and babysit all of this yourself, VigilDog's Ads MCP manages the token, OAuth, and login-customer-id plumbing for you, with every change dry-run and approval-gated. For the full picture of driving campaigns this way, see running Google Ads from Claude.

How an Ads MCP runs a change safely