One hosted server URL
Connect the remote Adscriptly MCP endpoint instead of running a local advertising connector or handling platform credentials in the chat client.
Meta Ads + AI clients
Hosted MCPAI connector
Bring Meta Ads reporting into any MCP-compatible AI client.
Connect the hosted Adscriptly MCP endpoint to a compatible AI client, authorize your Adscriptly workspace, and select an accessible Meta ad account. The current Meta Ads connection is read-only and focuses on aggregate account performance.
MA
Ad account
Meta Ads
Ac
AI client
AI clients
Intended outcome
Give an AI client authenticated Meta Ads evidence without granting it campaign-management permission.
Connection scope
Meta offers its own AI and connector products. This page covers the Adscriptly hosted MCP reporting path and does not imply an official Meta partnership.
What the connection does
Control what AI clients can access in Meta Ads.
Adscriptly OAuth sign-in
The client redirects to Adscriptly for authorization, so the resulting access stays tied to the authenticated workspace.
Meta Ads account context
Use selected Meta ad-account context and aggregate performance available to the authenticated business user.
Read-only platform scope
The current Meta Ads connection is read-only and does not request campaign-management permission.
Data flow
Know what moves between systems.
Meta AdsAdscriptly logicAI clients
Meta Ads
Authorized Meta Ads account
Adscriptly logic
Authenticated workspace and account selection
AI clients
AI clients tool context
Meta Ads
Natural-language request
Adscriptly logic
Adscriptly tool selection and schema validation
AI clients
Structured tool call
Meta Ads
Meta Ads response
Adscriptly logic
Normalize the result for the conversation
AI clients
Answer with account evidence
Meta Ads
Read request
Adscriptly logic
Read-only permission boundary
AI clients
No platform mutation
Setup
Connect AI clients to the hosted Adscriptly MCP server.
- 01
Copy the server URL
Use https://adscriptly.com/api/mcp as the remote MCP server address.
- 02
Add it to AI clients
Add the Adscriptly endpoint as a remote MCP server, then complete the Adscriptly OAuth redirect.
- 03
Sign in to Adscriptly
Complete the Adscriptly OAuth prompt and authorize the workspace the client should use.
- 04
Choose a Meta Ads account
Start with account discovery, select the intended Meta Ads account, and keep the workflow within the current read-only scope.
Connection controls
Review the account, permission scopes, and write approval settings.
- The AI client does not receive the underlying advertising-platform credential.
- Account context must resolve before an account-specific tool runs.
- The current platform path is read-only.
- The Adscriptly OAuth token can be revoked.
Related integrations
Integration FAQ
Before you connect.
What is the Adscriptly Meta Ads MCP server URL?
Use https://adscriptly.com/api/mcp. The hosted endpoint supports OAuth, so compatible clients can redirect you to Adscriptly to authorize access.
Does AI clients need my Meta Ads password or token?
No. Connect Meta Ads inside Adscriptly and authorize the MCP client through Adscriptly OAuth. The chat client does not need the underlying platform credential.
Can AI clients change Meta Ads campaigns?
The current Meta Ads connection is read-only and does not request campaign-management permission.
Is this an official Meta Ads or AI clients integration?
No partnership is implied. This is an Adscriptly-hosted MCP connection that uses the permissions granted to the authenticated Adscriptly workspace and the remote-connector support available in AI clients.
Meta Ads + AI clients
Use Meta Ads account data in AI clients.
Add the hosted MCP server, authorize Adscriptly, select the intended ad account, and begin with a read-only question.
