Meta Ads MCP
Access and review instructions
This page documents Silsal's internal Facebook OAuth and official Meta Ads MCP integration for reviewers. The integration is an operational tool for authorized Silsal operators, not a consumer social-login feature.
Where to find the app
This public page is the review entry point. An operator starts authorization from an MCP-compatible AI client connected to Meta's official endpoint at https://mcp.facebook.com/ads. OAuth then returns to the allowlisted secure callback on silsal.org.
Facebook Login use
Yes. The integration uses Facebook Login OAuth only so an authorized advertiser can grant access to ad assets they manage. Silsal never receives a Facebook password and does not offer public account creation through Facebook.
Meta APIs and permissions
The agent uses Meta's official Ads MCP server for consented ads management and reporting, business and catalog access, managed Page discovery, Instagram Basic, and ads_mcp_management. We do not request friends, gender, or birthday data, and email is not used for product functionality.
How to test
- Open this page and confirm it is publicly accessible without login or payment.
- Start OAuth from an MCP client connected to Meta's official Ads MCP endpoint using the silsal app.
- Sign in with a reviewer account that has access to a test ad asset and approve the displayed permissions.
- Confirm the agent can list accessible ad accounts and campaigns and read insights. Any advertising change requires an explicit operator request.
Access and restrictions
There is no payment, membership, in-app subscription, download fee, or geographic restriction for review. Personal credentials are not published; Meta reviewers can use their review account and a test ad asset they control.
Data and deletion
OAuth credentials are stored server-side and are never exposed to a browser or client bundle. A user can revoke access in Facebook settings or request deletion of integration data by emailing contact@silsal.org.