Sprites
Perplexity133d livePerplexity Computer
Add Sprites to GitHub Copilot
Available on Copilot in VS Code, and Copilot CLI. Any Copilot plan that includes agent mode. You need a Sprites account with Meta Ads already connected — the connector acts on that connection, so GitHub Copilot never handles a Meta credential.
Open the MCP configuration
Run MCP: Add Server from the Command Palette and choose Workspace or Global. Workspace writes .vscode/mcp.json, which is worth committing so the team shares the same connector; Global keeps it to you across every project.
VS CodeCommand PaletteMCP: Add ServerWorkspaceAdd Sprites as an HTTP server
The top-level key is servers, not mcpServers, and a remote endpoint needs an explicit type of http. This is the shape VS Code and Copilot share.
.vscode/mcp.json{ "servers": { "sprites": { "type": "http", "url": "https://mcp.sprites.ai/mcp" } } }Authenticate
VS Code shows an Auth action above the server entry once the file is saved. Run it, sign in to Sprites in the browser window that opens, and approve the scopes.
Spriteswants access on behalf of Copilot- Read your connected ad accounts and site data
- Draft campaigns, creatives and pages for your approval
- Apply only the changes you approve
AllowCancelSwitch Copilot Chat to agent mode
MCP tools are only offered to the agent. Pick Agent from the mode dropdown in Copilot Chat, then open the tool picker and confirm Sprites is listed.
Agent modeCopilot Chat → mode dropdown
Run the first prompt
Ask GitHub Copilot this. It routes to a Sprites door, which reads your Meta Ads account and answers — no account to name, no confirmation to give first.
- With Sprites, which Meta creatives are fatiguing and what should replace them?
- Ask Sprites for 5 new hooks for our best-performing Instagram ad.
- Use Sprites to compare Meta ROAS this month against last month by ad set.
- Have Sprites check whether our ad sets are overlapping on audience.
- With Sprites, show me what our top 3 competitors are running on Meta right now.
Open the Copilot Chat tool picker in agent mode; Sprites appears with its tools, each one toggleable.
What GitHub Copilot can do with Meta Ads
The same doors, whichever client you are in. Marketing data inside the editor where the tracking code lives, so a conversion event can be checked against what GA4 actually recorded before the pull request is opened.
See fatigue before the CPA does
Frequency, first-time impression ratio and the day a creative's CTR broke trend, per ad rather than per campaign.
Get new creative, not a brief
Hooks, headlines and image concepts drafted against what is already working, previewed in the real placement.
Untangle the ad sets
Audience overlap, learning-phase resets and the ad sets quietly bidding against each other.
Watch the competition
Live ads from any advertiser in the Meta ad library, read as angles rather than screenshots.
Launch across placements
Campaign, ad sets, audiences and ads in one editable proposal, with the creative attached.
Reallocate on evidence
Move budget to the ad set that earns it, with the before-and-after stated in the card.
How approvals work here
GitHub Copilot renders tool results as text, so a Meta change comes back written out rather than as a card. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
What it reads
- Campaigns, ad sets, ads, audiences and their status
- Spend, ROAS, CPA, CTR, frequency and placement breakdowns
- Creative assets and per-creative performance
- Public competitor ads from the Meta ad library
What it can change
- Create campaigns, ad sets, audiences and ads
- Budgets, schedules, statuses and targeting
- New creative, previewed in placement before anything ships
When it does not work in GitHub Copilot
Three things go wrong in this client specifically, and each has a one-line fix.
Sprites is configured but Copilot never uses it.
Chat is not in agent mode. Ask mode does not call MCP tools at all.
The config is ignored.
The top-level key is servers. mcpServers is the shape other clients use and VS Code does not read it.
Teammates do not see the connector.
It was added Globally rather than to the Workspace. Move it to .vscode/mcp.json and commit that file; each person still signs in as themselves.
Meta Ads and GitHub Copilot: questions
Which URL do I paste into GitHub Copilot?
https://mcp.sprites.ai/mcp. There is one endpoint and every client uses it — every OAuth grant is bound to exactly that address, so a variant of it will not be honoured.
Can GitHub Copilot change my Meta Ads account without asking?
GitHub Copilot renders tool results as text, so a Meta change comes back written out rather than as a card. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
Do I need a Meta Ads API key or developer token?
No. Meta Ads is connected once inside Sprites through Meta (Facebook and Instagram) Ads, and the connector acts on that connection. GitHub Copilot never sees a credential for it.
Why GitHub Copilot for Meta Ads specifically?
Marketing data inside the editor where the tracking code lives, so a conversion event can be checked against what GA4 actually recorded before the pull request is opened.
Do I need a Meta developer app or a system user token?
No. You connect Meta once inside Sprites with OAuth; the MCP connector then acts on that connection. Your agent never sees a token.
Can it publish an ad without me seeing it?
No. Creative comes back as a preview in the real placement, editable, and ships only when you approve it.
Keep going
The same GitHub Copilot connector reaches every other channel — nothing else to add.
Meta Ads, from GitHub Copilot
Paste one URL, sign in once, and the next Meta question you ask GitHub Copilot gets answered from the live account.