SpritesAdd 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 Business Profile already connected — the connector acts on that connection, so GitHub Copilot never handles a GBP 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 Google Business Profile account and answers — no account to name, no confirmation to give first.
- With Sprites, how did each of our locations perform in local search last month?
- Ask Sprites which of our listings are missing hours, categories or photos.
- Use Sprites to draft a seasonal post for the Portland location.
- Have Sprites list every location and what each one is missing.
- With Sprites, which searches are surfacing our Austin store?
Open the Copilot Chat tool picker in agent mode; Sprites appears with its tools, each one toggleable.
What GitHub Copilot can do with Google Business Profile
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.
Performance per location
Views, searches, calls and direction requests for each listing, not one rolled-up number.
Find the listings that are incomplete
Missing hours, wrong category, no photos — the fields that quietly keep a location out of the map pack.
Post without the tab
Updates and offers drafted per location and published on approval.
Pin a location and stay there
Multi-location accounts pin to one listing for a conversation, so an answer never silently switches store.
See which searches find you
The queries surfacing each listing, so the category and description can be argued from data.
Join it to the ads
Local performance next to the local campaigns spending against it, in one connector.
How approvals work here
GitHub Copilot renders tool results as text, so a GBP 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
- Every location on the account and its profile fields
- Views, searches, calls, direction requests and photo views
- The queries surfacing each listing
- Reviews and their ratings
What it can change
- Posts, updates and offers, per location
- Profile fields: hours, categories, description, attributes
- Each one approved before it publishes
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 Business Profile 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 Business Profile account without asking?
GitHub Copilot renders tool results as text, so a GBP 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 Google Business Profile API key or developer token?
No. Google Business Profile is connected once inside Sprites through Google Business Profile, and the connector acts on that connection. GitHub Copilot never sees a credential for it.
Why GitHub Copilot for Google Business Profile 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.
Does it handle more than one location?
Yes. Multi-location accounts list every location, report per location, and pin to one for the length of a conversation so an answer cannot drift to the wrong store.
Can it reply to reviews?
It reads reviews and can draft a reply, but the reply publishes only on your approval — a review response is not something to automate blind.
Keep going
The same GitHub Copilot connector reaches every other channel — nothing else to add.
Google Business Profile, from GitHub Copilot
Paste one URL, sign in once, and the next GBP question you ask GitHub Copilot gets answered from the live account.