Skip to main content
Glama
gudlab

ads-mcp

by gudlab

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
META_APP_IDYesMeta App ID from the Meta developer app.
META_APP_SECRETYesMeta App Secret from the Meta developer app.
META_ACCESS_TOKENYesLong-lived Meta System User access token with ads_management scope.
META_AD_ACCOUNT_IDYesNumeric Meta ad account ID (the client adds the act_ prefix).
GOOGLE_ADS_CLIENT_IDYesGoogle Cloud OAuth client ID (from a Desktop app OAuth client).
GOOGLE_ADS_CUSTOMER_IDYes10-digit Google Ads customer ID (no dashes).
GOOGLE_ADS_CLIENT_SECRETYesGoogle Cloud OAuth client secret (from a Desktop app OAuth client).
GOOGLE_ADS_REFRESH_TOKENYesGoogle Ads refresh token, generated by running the local OAuth flow.
GOOGLE_ADS_DEVELOPER_TOKENYesGoogle Ads API developer token, obtained from the Google Ads API Center.
GOOGLE_ADS_LOGIN_CUSTOMER_IDNoOptional MCC customer ID, only needed if the account is managed under an MCC account.

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

NameDescription

No tools

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources