You can connect Claude to Meta ads through ToMarket MCP, which gives the assistant access to supported campaign and reporting tools in your ToMarket workspace. The connection uses ToMarket authorization; it does not require you to paste a Meta access token into a conversation.
This article covers the connection itself. If your account is already connected and you want to create an ad, go to the Claude creative workflow.
Understand the two connections
There are two relationships to check. Your ToMarket workspace must have access to the advertising account, and Claude must be authorized to use the relevant ToMarket tools. A successful assistant connection cannot compensate for a missing advertising connection or insufficient account permissions.
This distinction is particularly useful when an agency works across client accounts. Seeing a workspace in the assistant does not prove that every client account inside the organization is available for every action. Confirm the business context instead of inferring it from a familiar company name.
Add the remote server in Claude
Open Claude's connector settings and add a custom remote connector. Enter the ToMarket server address:
https://api.tomarket.io/api/customer-mcp
Continue through the authorization screen, sign into the appropriate ToMarket account, and review the requested access. Follow Anthropic's current connector instructions if the menu labels differ in your account.
After connecting, ask Claude to identify the available workspace and advertising context. A read-only request is a useful first check because it separates connection testing from creative generation or campaign changes.
Confirm the account before asking for an action
Try: "Show me the advertising accounts available in this workspace and identify which one belongs to this offer." Compare the response with what you see in ToMarket.
If the assistant finds more than one plausible account, resolve that ambiguity before proceeding. The same applies to similarly named brands, offers, or campaigns. A clear request names the intended object and gives you a chance to review it.
Once you have confirmed context, ask for a campaign summary or a creative draft. Keep paid generation and launch decisions explicit. ToMarket's supported actions follow your permissions and enabled features.
When the connector option is missing
A missing custom-connector control is an assistant-account issue rather than proof that the ToMarket endpoint is wrong. Check the host's current availability and any organization restrictions. If you are in a managed workspace, your administrator may control which connectors can be added.
Avoid following an old screenshot step for step when the interface has changed. The important pieces are the remote server URL, the authorization flow, and the workspace you authorize.
When the connection exists but a tool cannot act
Check whether the requested action needs a connected Meta account, a different workspace permission, or an enabled feature. Also distinguish a connection error from a paid-action confirmation or a creative editor opening in the browser.
An editor link is not necessarily a failed connection. Interactive interfaces depend on host support, while supported browser workflows can still let you review the creative. The MCP release notes explain that distinction.
If you need help, send the assistant name, the point where the process stopped, and the visible error through ToMarket's integration form. Do not include tokens or passwords. A precise description of the failure is more useful than repeatedly reconnecting unrelated accounts.
Connecting the right account is the foundation. From there, ToMarket's Meta advertising tools supply the campaign context and supported actions that Claude can work with.
