Two surfaces, one tool layer
Foxley is Outfox’s first-party AI agent, used inside the Outfox app athttps://app.outfox.ai. The MCP suite is the same tool surface, exposed at https://app.outfox.ai/api/mcp so MCP clients (Claude, Claude Code, Cursor, …) can consume it from outside the Outfox UI.
Both surfaces share one tool layer. search_inspiration, generate_brief, meta_ads_get_insights, render_ui, and the rest are available in both. A campaign report you pull in Foxley matches the one you pull in Claude Desktop — both surfaces read and write the same data.
When to use Foxley
Reach for Foxley when the workflow benefits from being inside the Outfox app:- The brand or ad account you’re working on is already selected; no organization picker to walk through.
- You want to drag images, briefs, or ad screenshots into the chat and have the agent see them.
- You want generative UI charts rendered inline next to the brand they describe.
- You want clickable affordances — open a brand profile, jump into an analysis run, pull up an inspiration post — without leaving the conversation.
- You want the in-app extras: voice conversations, saved routines, and your own MCP connectors.
- You’re a marketer or operator who doesn’t run an MCP client and doesn’t want to set one up.
When to use the MCP suite
Reach for the MCP suite when the work belongs in a tool you already use:- You’re researching or strategizing in Claude or Claude Code and want Outfox tools available in the same thread as everything else.
- You’re building in Cursor and want Outfox callable from your coding assistant.
- You’re running Outfox alongside other MCP servers in a cross-tool workflow.
- You want programmatic or scripted access — agent loops, batch operations, scheduled runs — that aren’t a conversation a person sits through.
- You’re wiring Outfox into a custom agent on top of the MCP spec.
What’s the same
Both surfaces share:- The tool surface. Same tool names, same parameters, same results.
- Organization, brand, and ad-account scoping. Both honor your organization’s membership and brand ownership.
- Attribution policy. A per-account window set with
meta_ads_set_attribution_modeapplies to insights calls on either surface. - The data. A campaign list or inspiration search returns the same rows in either place.
What’s different
| Foxley | MCP suite | |
|---|---|---|
| Where it runs | Inside the Outfox web app | Inside your MCP client (Claude, Cursor, …) |
| Sign-in | You’re already signed in to Outfox | OAuth via Clerk on first connect |
| Brand context | Pre-selected based on the page you opened it from | Ask the model to list and pick a brand |
| File uploads in chat | Drag images and briefs directly into the conversation | Depends on the client |
| Generative UI charts | Always rendered as interactive charts and panels | Rendered in clients that support generative UI; other clients see the raw spec as text |
| Model | Picked by Outfox | Whatever model your client runs |
| Mixing servers | Foxley is its own thread | Outfox sits alongside the other MCP servers you’ve added |
Switching between
You don’t migrate. Foxley and the MCP suite read and write the same brands, ad accounts, analyses, and inspiration runs.- A Foxley user who also wants to drive Outfox from Cursor: open Cursor, point it at
https://app.outfox.ai/api/mcp, sign in with the same account. - An MCP-client user who wants to try Foxley: open
https://app.outfox.aiand start a chat.
What to open next
Quickstart
Connect an MCP client and run your first tool call.
Foxley in the app
Voice mode, routines, connectors, and slash commands inside Outfox.
Platform overview
See the tool families and how they fit together.
Generative UI
Check whether your MCP client renders interactive charts.
Meta MCP parity
Compare the Outfox
meta_ads_* tools to Meta’s official MCP.