Google Ads MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_PROJECT_ID | No | Your Google Cloud project ID. | |
| GOOGLE_ADS_MCP_BASE_URL | No | Base URL where the server is accessible (default http://localhost:8080). | |
| GOOGLE_ADS_DEVELOPER_TOKEN | No | Your Google Ads developer token. | |
| GOOGLE_ADS_MCP_TOOLS_CONFIG | No | Path to tools configuration YAML file. | |
| GOOGLE_ADS_LOGIN_CUSTOMER_ID | No | Manager customer ID for login. | |
| GOOGLE_ADS_MCP_OAUTH_CLIENT_ID | No | OAuth 2.0 Client ID for OAuth proxy authentication. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to Google Application Default Credentials JSON file. | |
| GOOGLE_ADS_MCP_OAUTH_CLIENT_SECRET | No | OAuth 2.0 Client Secret for OAuth proxy authentication. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/georgebrinckmann/google-ads-mcp-write'
If you have feedback or need assistance with the MCP directory API, please join our Discord server