What you need to know
- Meta Ads MCP connects an assistant to authorized Facebook and Instagram advertising tools; the connector does not grant access to accounts you do not own or manage.
- In PlugMind, connect Meta and select an ad account inside the intended client workspace before asking your assistant for a report.
- A successful assistant login does not prove that the Meta grant, ad account selection, and every optional permission are ready.
Understand the three connections
Start with the account you want to analyze, not the assistant you want to use. Write down the client workspace name and the Meta ad account ID. An agency can have several workspaces with similar names, and the same Facebook login can have access to several businesses. This small check prevents a technically successful connection from reporting on the wrong client.
| Layer | What it controls | How to check |
|---|---|---|
| Assistant → PlugMind | Which PlugMind user is calling tools | Sign in to the intended PlugMind account during OAuth. |
| PlugMind workspace | Your role and the selected client account | List accessible workspaces, then verify the selected Meta account. |
| PlugMind → Meta | Granted permissions and available assets | Check the live Meta grant and a read-only account request. |
MCP carries tool requests between the assistant and server. Meta authorization remains a separate requirement. A connector showing “connected” is therefore the beginning of the check, not evidence that campaign creation, lead retrieval, and Page access all work.
Connect the workspace before the assistant
- 1
Choose the client workspace in PlugMind
Sign in to PlugMind and open the workspace for the client you intend to test. Use an account with the role needed for the work. Keep unrelated clients in their own workspaces.
- 2
Connect Meta and choose the ad account
Complete Meta authorization with a person who has access to the intended assets. Back in PlugMind, select the correct ad account. Record its ID; account names alone are not a reliable identifier.
- 3
Connect a supported MCP client
Use the PlugMind endpoint https://www.plugmind.io/mcp and complete PlugMind OAuth in a client that supports remote MCP. ChatGPT availability depends on your plan, workspace controls, and app availability; do not assume a public directory listing is available. Use the current setup path provided for your account.
- 4
Run a read-only check
Ask the assistant to list your accessible workspaces and the Meta ad account selected for the chosen workspace. Resolve any mismatch before retrieving reports or proposing a campaign change.
Check permissions for the task you actually need
PlugMind exposes get_meta_permission_readiness for inspecting the live grant. It reports required, granted, missing, and ready values rather than relying only on the scopes saved when the account was first connected. Use that result when an older connection seems to be missing a newly introduced tool.
The integration requests ads_read and ads_management for advertising workflows, business_management for business assets, Page-related scopes for Page workflows, and leads_retrieval for lead forms. This is PlugMind’s requested scope set, not a guarantee that every token has every permission or that every user can access every asset.
- A missing advertising permission and an unselected ad account are different problems. Fix the cause reported by the tool.
- A user’s consent cannot replace their business or ad account role. Verify ownership and assignment in Meta as well.
- Do not collect lead contact details for a basic campaign audit. Aggregated campaign metrics are enough for an initial reporting check.
Troubleshoot the first failed request
| Symptom | Check first | Next action |
|---|---|---|
| Workspace not found | The authenticated PlugMind user and exact workspace name | List accessible workspaces; do not guess another client’s ID. |
| No ad account selected | Account selection inside that workspace | Choose an authorized Meta ad account in PlugMind. |
| Missing scopes or expired authorization | Live permission-readiness result | Use the reconnect link returned by PlugMind, then recheck. |
| Read succeeds but a write fails | Role, asset access, required fields, and exact Meta error | Correct the specific issue and validate a fresh proposal. |
| Spend differs from Ads Manager | Account, dates, time zone, filters, and metric definitions | Match the reporting settings before drawing conclusions. |
Keep the exact error message and code. Repeating the same campaign creation request after an uncertain response can produce duplicate work. Check whether the object exists and prepare a fresh validated proposal before seeking approval again. For sign-in problems, reconnecting the assistant alone may not refresh the underlying Meta grant.
Verify one report before asking for changes
Compare one campaign with Ads Manager using the same period and columns. An empty report is not automatically a failed connection: the account may have no delivery in the requested window. If the raw totals match, move to a broader audit. If they do not, resolve the measurement difference first.
Campaign creation is a separate test. PlugMind’s Meta workflow validates the proposal, asks for explicit approval, and creates new advertising objects paused. Enabling an object can start delivery and spending, so it requires a separate decision. A working report does not certify the write path.
Frequently asked questions
Does Facebook Ads MCP mean something different from Meta Ads MCP?
In this guide both refer to connecting Meta’s paid advertising tools to an assistant. Available placements and assets still depend on the account and campaign configuration.
Do I need to paste a Meta access token into ChatGPT?
No. Use the supported OAuth connection. Do not paste passwords, access tokens, or app secrets into a conversation.
Can I use this to access a client account without permission?
No. The workspace membership, Meta authorization, and asset assignment must all permit the request.
Sources and verification
Platform references are listed below. PlugMind tool descriptions were checked against its implementation. Example prompts are suggested workflows, not claims of results from a live advertising account.
