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 Google Ads already connected — the connector acts on that connection, so GitHub Copilot never handles a Google Ads 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
Official Google Ads MCP vs Sprites MCP
Google runs its own MCP server at github.com/googleads/google-ads-mcp. Here is what each one covers, so you can pick the one that fits in GitHub Copilot — or connect both.
Google publishes its own Google Ads MCP server as open source. It has three tools — a GAQL query runner, resource metadata and a list of accessible accounts — and it is read-only by design: in Google’s words it "cannot modify bids, pause campaigns, or create new assets." Google does not host it. You run it locally with pipx or deploy it to your own Cloud Run, with your own OAuth credentials and a developer token.
| Google officialgithub.com/googleads/google-ads-mcp | Sprites MCPapproval-gated | |
|---|---|---|
| Where it runs | Your machine, or your own Cloud Run deployment | Hosted: paste mcp.sprites.ai/mcp and sign in |
| Credentials | Your OAuth client and a developer token with at least Explorer access | None to manage — Google Ads is connected once through a Google Partner integration |
| Tools | Three: GAQL search, resource metadata, accessible customers | Broad doors: analyze, optimize, launch, change |
| Writes | None — read-only by design | Budgets, bids, keywords, ads and campaigns, each an approval card applied only on approve |
| Analysis | Returns rows for the model to reason over | A Google Ads specialist reads search terms, change history and impression share before answering |
| Channels | Google Ads | Google Ads plus Meta, LinkedIn, TikTok, Reddit, GA4 and SEO |
| Best at | Precise reporting queries, for people comfortable with GAQL and a terminal | Deciding what should change, and changing it with your approval |
If you want exact answers to reporting questions and are happy to run a Python package with your own credentials, Google’s server is excellent and free. Use Sprites when you want the answer to turn into a change — a budget moved, a keyword paused, a campaign launched — without hosting anything, or when Google Ads is one channel of several.
Run the first prompt
Ask GitHub Copilot this. It routes to a Sprites door, which reads your Google Ads account and answers — no account to name, no confirmation to give first.
- With Sprites, how did Google Ads do last 30 days vs the 30 before?
- Use Sprites to find search terms that spent over $50 with no conversion last month.
- Ask Sprites to build a Search campaign for our pricing page at $80/day.
- Have Sprites raise the Brand — Exact budget to $65/day and tell me why first.
- With Sprites, which campaigns are losing impression share to budget rather than rank?
Open the Copilot Chat tool picker in agent mode; Sprites appears with its tools, each one toggleable.
What GitHub Copilot can do with Google 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.
Ask about last week in the thread you are already in
Spend, conversions, CPA, ROAS and the period comparison, read from the live account rather than a stale export.
Find the waste before it compounds
Search terms with cost and no conversion, broad-match drift, and the negatives that would have stopped it.
Launch without the wizard
Campaign, ad group, responsive search ads and keywords arrive as one editable proposal rather than nine screens.
Change one thing precisely
Raise a budget, pause a campaign, add a negative — one approval card, applied on your click.
Ask why, not just what
Impression share lost to rank and to budget, auction pressure, and which of the two actually moved.
Leave a standing order
A Monday morning brief or a nightly waste check that runs on schedule and messages you only when it matters.
How approvals work here
GitHub Copilot renders tool results as text, so a Google Ads change comes back written out rather than as a card. The approval waits for you in Sprites — open it there and the same run continues. Nothing is applied until you approve it.
What it reads
- Campaigns, ad groups, ads, keywords and their status
- Spend, impressions, clicks, conversions, CPA, ROAS and impression share
- Search terms, assets and asset performance labels
- Change history, so a drop can be traced to an edit
What it can change
- Create campaigns, ad groups, responsive search ads and keywords
- Budgets, bids, statuses, negatives and targeting
- Nothing applies without an approval you have seen and clicked
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.
Google 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 Google Ads account without asking?
GitHub Copilot renders tool results as text, so a Google Ads change comes back written out rather than as a card. The approval waits for you in Sprites — open it there and the same run continues. Nothing is applied until you approve it.
Do I need a Google Ads API key or developer token?
No. Google Ads is connected once inside Sprites through Google Ads (official Google Partner OAuth), and the connector acts on that connection. GitHub Copilot never sees a credential for it.
Why GitHub Copilot for Google 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.
Is there an official Google Ads MCP server?
Yes. Google publishes googleads/google-ads-mcp: open source, read-only by design, and not hosted by Google — you run it locally or on your own Cloud Run with your own API credentials. Sprites is a separate, hosted server that reads and changes Google Ads through a Google Partner integration, with every change held for approval.
Is this a Google Ads MCP server I have to host?
No. Sprites is a hosted remote MCP server: you paste one HTTPS URL into your agent and sign in. There is nothing to install, no developer token to obtain, and no API credentials to store on your machine.
Keep going
The same GitHub Copilot connector reaches every other channel — nothing else to add.
Google Ads, from GitHub Copilot
Paste one URL, sign in once, and the next Google Ads question you ask GitHub Copilot gets answered from the live account.