Cursor

Gummble gives Cursor design evidence from 300,000+ real app screens, 21,000+ browsable flows, and 1,500+ apps and sites. The server exposes exactly 14 read-only tools for finding screens, flows, patterns, store screenshots, and UX microcopy. It cannot edit your project or mutate Gummble data.

Access and trial eligibility are determined by the Gummble account you use to sign in. A trial is not guaranteed.

1. Add the server

Click Add gummble to Cursor and confirm the new MCP server when Cursor opens.

The install page shows the remote URL before it opens Cursor. It does not embed an API key or bearer token.

For a manual install, add this entry to ~/.cursor/mcp.json (all projects), or to .cursor/mcp.json inside one project:

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

2. Sign in

Open Cursor Settings → Tools & MCP, select gummble, and start the sign-in flow. Your browser opens Gummble OAuth; sign in on gummble.com and approve the connection. Cursor can also prompt for authorization on the first tool call.

If you use Cursor's CLI, authenticate the configured server with:

agent mcp login gummble

3. Verify

Check that Cursor can discover the exact tool inventory:

agent mcp list-tools gummble

Then run a real request in Cursor chat:

Use Gummble MCP to find 3 fintech onboarding screens and cite the app for each result.

A successful Gummble result confirms both OAuth and tool access. Do not count a copied command or an opened OAuth tab as an activation.

Troubleshooting

If Cursor connects but returns no tools, re-authorize Gummble and check Troubleshooting. If OAuth opens but never completes, start with OAuth opens but fails.

If the server appears twice, keep gummble in only one scope: either the global file or the project file.

Cursor references

• Cursor MCP configuration
• Cursor MCP install links
• Cursor CLI MCP commands