The design MCP server for Cursor.

One click connects Cursor to 300,000+ real app screens, 21,000+ flows, and searchable microcopy — so Agent mode references shipped UI while it builds yours.

Add gummble to Cursor Check trial eligibility

Included in all paid plans from $9.99/mo. Trial eligibility is shown at checkout. OAuth — no API key.

~/.cursor/mcp.jsongummble · 14 tools

{
  "mcpServers": {
    "gummble": {
      "url": "https://mcp.gummble.com/mcp"
    }
  }
}

agent

Searching gummble for real checkout forms…

⏺ gummble_search_screens · 38 results → editing checkout-form.tsx

Add Gummble MCP to Cursor

The one-click link is fastest. The manual entry does exactly the same thing — pick whichever fits how you manage your editor config.

Option A — one click

Cursor opens and asks you to confirm the server. Nothing else to edit.

Add gummble to Cursor

Option B — edit mcp.json

Add this entry to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project only).

{
  "mcpServers": {
    "gummble": {
      "url": "https://mcp.gummble.com/mcp"
    }
  }
}

2
Authorize
Click Sign in next to gummble in Cursor's MCP settings. Sign in with your Gummble account to authorize access.
3
Verify the connection
Paste this prompt into Cursor Agent. A Gummble result confirms both OAuth and tool access.
4
Verify the connection
Open Cursor Settings → MCP. The gummble entry should show a green status with a14-tool count. If it doesn't, the troubleshooting section below covers the usual causes.

What Cursor does with it

Cursor's edge is that references land while you're editing the file. These prompts pair a Gummble search with a concrete change to your code.

Reference before you style

Find 5 real checkout forms on gummble and list the trust elements they place near the pay button, then apply that pattern to checkout-form.tsx.

The agent studies shipped checkouts first, then edits your actual file — reference and implementation in one loop, without leaving the editor.

gummble_search_screensgummble_get_screen_detail

Match a proven flow

Search gummble for search-results screens in travel apps, pick the one with the best information density, and restyle SearchResults.tsx to match its layout decisions.

Instead of debating density in the abstract, Cursor anchors the refactor to a screen that already works in production.

gummble_search_screensgummble_find_similar_screens

Fix the words, not just the UI

Pull error-state microcopy for form validation from gummble and rewrite the error strings in this file to match the clearest pattern.

Microcopy is where generated UI usually sounds fake. Real validation copy from real apps fixes the tone in one pass.

gummble_search_microcopy

The full tool catalog — 7 search tools, 5 lookup tools, and 2 batch variants, all read-only — is documented on the Claude Code guide and works identically in Cursor.

Troubleshooting in Cursor

The four issues that cover nearly every failed setup, with the fix for each.

The server shows red or lists no tools

Open Cursor Settings → MCP and check the gummble entry. The most common cause is a JSON syntax slip in mcp.json — a missing comma or brace. Fix the entry, then toggle the server off and on (or restart Cursor) to reconnect.

No sign-in window appeared

Cursor starts OAuth from the MCP settings list, not automatically. Find gummble in Settings → MCP and click Sign in (Needs login) next to it, then approve access in the browser tab that opens.

The server isn't picked up at all

Remote HTTP servers need a recent Cursor build. Update Cursor, then confirm your entry uses the url field exactly as shown above. If your build still can't connect, file location matters too: the global file is ~/.cursor/mcp.json, not the project one.

Tools exist but the agent never calls them

Cursor's agent decides when a tool is relevant. Name the server in your prompt — 'search gummble for …' — and it will call the right tool. You can also confirm tools are available from the tool count in Settings → MCP.

Safe to leave connected.

Cursor's agent calls tools on its own, so the server it talks to should have nothing dangerous to call.

Read-only by design

All 14 tools are search and lookup with read-only annotations. No write access to Gummble, and no access to your codebase — only Cursor touches your files.

OAuth, not API keys

The only thing in mcp.json is a URL. Commit it, share it, paste it in a screenshot — there is no secret to leak. Revoke access any time from your Gummble account.

Plan-scoped and rate-limited

Requests are checked against your plan entitlement and fair-use rate limits, so an agent loop can't run up anything on your account.

Cursor questions, answered.

How do I add the Gummble MCP server to Cursor?

Two ways: click the one-click install link on this page (Cursor opens and asks you to confirm), or add a gummble entry with the server URL to ~/.cursor/mcp.json. Then sign in from Cursor Settings → MCP. No API key is needed.

Should I use the global or the project mcp.json?

~/.cursor/mcp.json makes Gummble available in every project. A .cursor/mcp.json file inside a repo scopes it to that project — commit it and teammates get the server too, each signing in with their own Gummble account.

Does Gummble MCP work in Cursor's Agent mode?

Yes. Once connected, the agent calls Gummble tools on its own when a prompt asks for design references — searching screens, expanding flows, or pulling microcopy while it edits your code.

Can Cursor write or delete anything through Gummble MCP?

No. All 14 tools are read-only search and lookup operations with read-only annotations. The server has no write access to Gummble and no access to your codebase — only Cursor touches your files.

Do I need an API key?

No. Gummble MCP authenticates with OAuth through your browser, so there is nothing to paste into mcp.json except the URL — and nothing to leak if you commit the file.

Which Gummble plan do I need?

MCP access is included on every paid plan, starting at $9.99/month. Check the pricing page and checkout for current trial eligibility before subscribing.

How do I remove the server?

Delete the gummble entry from your mcp.json (global or project), or remove it from Cursor Settings → MCP. You can also revoke the OAuth grant from your Gummble account settings.

Keep going

Server URL: https://mcp.gummble.com/mcp · Streamable HTTP · legacy SSE at /sse