Google Ads Transparency MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your own Apify API token. Required for the local stdio server; it is sent only in the Authorization header to the hosted Apify MCP endpoint. Without a token, tools/call returns a clear error instead of running anything. (When using the hosted endpoint directly, you can instead sign in with Apify OAuth when your client prompts you, or send the header `Authorization: Bearer <APIFY_TOKEN>`.) | |
| APIFY_ACTORS | No | Optional comma-separated subset of the Actors exposed by the server. | |
| APIFY_MCP_URL | No | Optional full endpoint override for the hosted Apify MCP endpoint. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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 | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues