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 SEO and Search Console already connected — the connector acts on that connection, so GitHub Copilot never handles a SEO 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 SEO and Search Console account and answers — no account to name, no confirmation to give first.
- With Sprites, write a post on "programmatic SEO for SaaS" and put it in WordPress as a draft.
- Ask Sprites which queries we rank 8-20 for and could reach the top 5.
- Use Sprites to optimize our /pricing page for "ai ads platform pricing".
- Have Sprites do keyword research for the integrations section and cluster it by intent.
- With Sprites, find pages that lost position in the last 28 days and say why.
Open the Copilot Chat tool picker in agent mode; Sprites appears with its tools, each one toggleable.
What GitHub Copilot can do with SEO and Search Console
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.
It writes onto the site, not into the chat
WordPress, Webflow, Shopify, Framer or a custom CMS: the post lands as a draft with metadata and internal links already set.
Keyword research with real numbers
Volume, difficulty and intent clustering from live data, not a model's recollection of a keyword tool.
Edit a page without breaking it
Page edits arrive as a diff. You see exactly which block changes before anything touches the live site.
Read what Search Console knows
Queries you nearly rank for, pages that slipped, and the impressions you are leaving on the table.
Internal links that already exist
New posts link into the site's real structure, because Sprites has read it.
Metadata that is not an afterthought
Titles, descriptions, focus keyphrases and schema written with the page rather than bolted on.
How approvals work here
GitHub Copilot renders tool results as text, so a SEO 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
- Search Console queries, impressions, clicks and average position
- Your live site: structure, internal links, existing pages and voice
- Keyword volume, difficulty and SERP composition
- What currently ranks for the target query
What it can change
- Blog posts, created as drafts in your CMS
- Landing and service pages, created or edited as a reviewable diff
- Titles, meta descriptions, focus keyphrases, headings and schema
- Publishing is always a separate, explicit approval
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.
SEO and Search Console 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 SEO and Search Console account without asking?
GitHub Copilot renders tool results as text, so a SEO 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 SEO and Search Console API key or developer token?
No. SEO and Search Console is connected once inside Sprites through Google Search Console and your CMS, and the connector acts on that connection. GitHub Copilot never sees a credential for it.
Why GitHub Copilot for SEO and Search Console 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.
Which content management systems does it publish to?
WordPress, Webflow, Shopify's blog, Framer, and any other CMS through a webhook. The CMS is connected once in Sprites; your agent never handles the credential.
Will it publish without asking?
No. Posts arrive as drafts and page edits arrive as diffs. Publishing is a separate approval, and a page edit shows you every block it would change.
Keep going
The same GitHub Copilot connector reaches every other channel — nothing else to add.
SEO and Search Console, from GitHub Copilot
Paste one URL, sign in once, and the next SEO question you ask GitHub Copilot gets answered from the live account.