Schema | Meta Ads MCP Server

Meta Ads MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`JWT_ISSUER`	No	Optional expected JWT issuer.
`JWT_SECRET`	No	Shared secret used to verify incoming MCP bearer JWTs (HS256).
`META_APP_ID`	Yes	Your Meta developer app ID.
`JWT_AUDIENCE`	No	Optional expected JWT audience.
`JWT_JWKS_URL`	No	JWKS URL used to verify incoming MCP bearer JWTs.
`APP_UI_USER_ID`	No	User ID used by the built-in admin UI.	app_admin
`APP_UI_PASSWORD`	Yes	Password for the built-in admin page at /app.
`META_APP_SECRET`	Yes	Your Meta developer app secret.
`META_OAUTH_SCOPES`	No	Comma-separated OAuth scopes requested during Meta login.	ads_management,business_management
`META_REDIRECT_URI`	No	OAuth callback URL, e.g. https://<your-worker-host>/oauth/meta/callback.
`APP_SESSION_SECRET`	No	Optional secret for the built-in admin page session.
`META_GRAPH_VERSION`	No	Meta Graph API version to use.	v25.0
`APP_UI_WORKSPACE_ID`	No	Workspace ID used by the built-in admin UI.	workspace_admin
`META_TOKEN_ENCRYPTION_KEY`	Yes	Key used to encrypt stored Meta access tokens.
`META_OAUTH_ALLOWED_RETURN_ORIGINS`	No	Comma-separated list of origins allowed for post-OAuth browser redirects, e.g. https://your-ui.example.com,http://localhost:3000.

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.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityActive

ResponsivenessNo issues