Sprites MCP · Agents · Cursor

Connect Cursor to Live Marketing Data With MCP

Cursor connects to remote MCP servers from an mcp.json file, either per project or globally, and handles the OAuth flow itself. Sprites is the one that carries marketing data, which matters in an editor because the page you are changing and the campaign pointing at it are finally in the same window.

MCP server URLhttps://mcp.sprites.ai/mcp

15 channels · 4 steps

CursorSprites connected

Where is Google Ads wasting money this month?

Spritesoptimizerunning
SpritesGoogle AdsNeeds your approval
  • Generic — Broad$1,240 · 0 convPause−$1,240
  • "free crm software"search termNegate−$380
  • Brand — ExactIS lost to budget 41%Raise+$25/day
3 changes proposed · nothing appliedReview

Add Sprites to Cursor

Available on Any Cursor plan that allows MCP servers, on desktop and on Cursor web agents. You need a Sprites account with your channels already connected — the connector acts on that connection, so Cursor never handles a platform credential.

  1. Write the config

    Put the entry in ~/.cursor/mcp.json to have Sprites available in every project, or in .cursor/mcp.json inside one repo to scope it there.

    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "sprites": {
          "url": "https://mcp.sprites.ai/mcp"
        }
      }
    }
  2. Or add it from the UI

    Cursor lists MCP servers under Customize in the sidebar; adding one there writes the same file.

    Cursor
    CustomizeMCPNew MCP server
  3. Sign in

    Cursor finds the Sprites authorization server from the endpoint's protected-resource metadata, registers itself, and opens a browser for the consent screen. Desktop completes on http://localhost:8787/callback and web agents on cursor.com; both are pre-registered, so there is nothing to allowlist.

    Spriteswants access on behalf of Cursor
    • Read your connected ad accounts and site data
    • Draft campaigns, creatives and pages for your approval
    • Apply only the changes you approve
    AllowCancel
  4. Keep it in the repo, not in your dotfiles

    A project-scoped .cursor/mcp.json is worth committing: every teammate who opens the repo gets the same connector and signs in as themselves. The file holds a URL and nothing else — the token is per person and never touches the config.

What Cursor can reach

All 15 channels run through the one connector. Rows with a guide go deeper on that pairing; the rest are covered on the channel's own page.

ChannelWhat Cursor does with itGuide
Google AdsChange the pricing copy and update the ads that quote it without a second tool.Set up →
MetaCreative and landing page reviewed together, since the mismatch between them is usually the problem.Set up →
LinkedInCost per lead by job function, ABM account lists, sponsored content that converts.Set up →
TikTokCPA and CTR for every ad, the next creative batch, and spend moved before the CPA drifts.Set up →
RedditCommunity targeting, subreddit-native copy, and the ad groups spending without converting.Set up →
GA4Live GA4 next to the instrumentation, which is the only place a tracking bug is cheap to find.Set up →
PostHogFunnels, retention and trends by campaign, read-only, beside the spend that bought them.Set up →
SEOSearch Console evidence beside the template that produces the pages it is about.Set up →
AEOWho gets cited by ChatGPT and Perplexity for your prompts, and the pages that change it.Set up →
ShopifySEO titles across the whole catalogue, collection pages, and product copy that ships on approval.Set up →
GBPPerformance per location, the listings missing fields, and posts that keep the map pack.Set up →
WordPressResearched posts, page edits and metadata written into WordPress as drafts you approve.Set up →
WebflowResearched CMS posts, page metadata and copy edits, each an approval before it applies.Set up →
FramerResearched posts and SEO fields written into your Framer CMS, added after you approve.Set up →
Zoho CRMPipeline and lead-source reporting beside ad spend, with approved lead, deal and note writes.Set up →

Marketing workflows worth doing in Cursor

The campaign and the page it points at live in the same window: change the pricing copy, then have Sprites update the ads that quote it, without a second tool.

Diagnose tracking against live GA4

Read what analytics actually recorded while looking at the code that fires it, instead of deploying and waiting to find out.

Update a landing page from campaign evidence

The search terms that are really converting, applied to the copy of the page they land on, in one pass.

Query Search Console while fixing templates

Which URLs on this template lost position, checked without leaving the file that generates them.

Build internal campaign dashboards

Real account data to develop against, so an internal reporting tool is built against the real shape rather than a fixture.

Permissions, approvals and authentication

You sign in with OAuth and the connector acts on your workspace. No API keys in a config file, no shared service account, and revoking the grant kills the very next call.

ActionWhen it happensWhat that covers
Read an accountOn requestSpend, performance, search terms, rankings, catalogue
Draft a changeOn requestCampaigns, creative, budgets, pages and posts
Apply a changeOnly on your approvalCursor returns the change as text; the approval waits for you in Sprites
Spend moneyOnly on your approvalNew campaigns start paused unless you say otherwise
Revoke accessInstantlyThe next call after a revoke fails, not the one after that

Cursor MCP questions

Project config or global?

.cursor/mcp.json in a repo scopes it to that project and is worth committing — everyone gets the same connector and signs in as themselves. ~/.cursor/mcp.json gives it to you everywhere.

Is this a coding-server directory page?

No. It is for growth engineers and technical marketers who want live account data in the editor. Cursor's general MCP directory is a different thing.

The Connect button does nothing.

A known issue on some Cursor builds. Update Cursor, remove and re-add the server, and if it persists restart with the config already in place so the connection is made at startup.

Can it change my ad accounts on its own?

No. Reads happen on request; every write comes back as a change you approve first, and new campaigns start paused. Nothing is applied because a model decided it should be.

Does the token go in the committed file?

No. The file holds a URL. The token is per person, obtained through the browser and held by Cursor, so committing the config shares the connector without sharing access.

Background worth having first

What the protocol is, how the servers differ, and what separates an agent from an assistant with tools attached.

Point Cursor at your ad accounts

One URL, one sign-in, and the next question you ask Cursor about your marketing gets answered from the live account.