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 LinkedIn Ads already connected — the connector acts on that connection, so GitHub Copilot never handles a LinkedIn 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 LinkedIn Ads account and answers — no account to name, no confirmation to give first.
- With Sprites, what is our LinkedIn CPL by job function this quarter?
- Use Sprites to build an ABM campaign for Series B fintechs in the US, 200-1000 employees.
- Ask Sprites which LinkedIn audiences are saturated and should be rotated.
- Have Sprites draft 3 new sponsored-content intros for our best-performing lead-gen form.
- With Sprites, compare LinkedIn spend and leads this month against last month.
Open the Copilot Chat tool picker in agent mode; Sprites appears with its tools, each one toggleable.
What GitHub Copilot can do with LinkedIn 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.
Cost per lead that names the segment
CPL by job function, seniority, company size and account, not one number for the whole account.
Build the ABM list in the chat
ICP criteria in, a matched company audience out, with the reach per tier stated before you spend.
Multi-thread the buying committee
Separate audiences for the champion, the economic buyer and the blocker, each with its own message.
Refresh sponsored content
New intros and creative drafted against what already converts, previewed in the feed.
Catch the quiet CPL drift
Frequency, audience saturation and the week the form fill rate started sliding.
Report without exporting
A period comparison your agent can read aloud, sourced from Campaign Manager rather than a slide.
How approvals work here
GitHub Copilot renders tool results as text, so a LinkedIn 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, campaign groups, creatives and audiences
- Spend, impressions, clicks, leads, CPL and form completion rate
- Demographic breakdowns: function, seniority, company, industry
- Matched-audience size and account coverage
What it can change
- Create campaigns, audiences, matched account lists and creatives
- Budgets, schedules, bids, targeting and status
- All of it gated behind an approval card
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.
LinkedIn 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 LinkedIn Ads account without asking?
GitHub Copilot renders tool results as text, so a LinkedIn 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 LinkedIn Ads API key or developer token?
No. LinkedIn Ads is connected once inside Sprites through LinkedIn Campaign Manager, and the connector acts on that connection. GitHub Copilot never sees a credential for it.
Why GitHub Copilot for LinkedIn 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.
Does it work with LinkedIn lead-gen forms?
Yes. Form completion rate and cost per lead are read per campaign and per segment, and new lead-gen campaigns are built with the form attached.
Can it upload a target account list?
It builds one. Give it the ICP criteria and it matches companies into a LinkedIn matched audience, showing the reach per tier before anything runs.
Keep going
The same GitHub Copilot connector reaches every other channel — nothing else to add.
LinkedIn Ads, from GitHub Copilot
Paste one URL, sign in once, and the next LinkedIn question you ask GitHub Copilot gets answered from the live account.