Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.universalbench.dev/llms.txt

Use this file to discover all available pages before exploring further.

Cursor speaks MCP natively. Adding UniversalBench takes about 30 seconds because there is no header config to fight with.

​
Setup

1

Get your personal MCP URL

Sign up at universalbench.dev. Your dashboard shows your URL: https://mcp.universalbench.dev/u/ub_live_xxxxxxxxxxxxxxxxxxxxx. Copy it.
2

Open Cursor MCP settings

Cmd+, on macOS, Ctrl+, on Windows. Search for “MCP” and click “Edit in settings.json”, or open the MCP config UI directly.
3

Paste the URL

{
  "mcpServers": {
    "universalbench": {
      "url": "https://mcp.universalbench.dev/u/ub_live_xxxxxxxxxxxxxxxxxxxxx"
    }
  }
}
Notice there is no headers block. The URL is the auth. This is by design and avoids Cursor’s intermittent header passing issues.
4

Restart Cursor

UniversalBench tools appear in the Composer’s tool list. Look for capabilities like db_select, safe_deploy, parallel_blocks.

​
What you can do now

Ask the Cursor Composer things that previously failed:
Refactor app/payments.py to use Stripe Checkout. Validate it compiles and passes my smoke test at /health before pushing.
Cursor will use safe_deploy to lint and validate the new code, push it to your branch, hit your smoke test URL, and auto rollback if the deploy breaks anything. Or:
How many users signed up yesterday? Pull from the users table.
Cursor uses db_select to query your database directly, returning the count without dumping every row into its context window.

​
Tips

Cursor’s Composer rate limits MCP tool calls per session. If you hit limits, batch operations through UniversalBench’s parallel_blocks to do more work per call.
Pin the UniversalBench tool group in Composer’s tool picker so it is always at the top of the list when you need it.

​
Troubleshooting

ProblemFix
Tools do not appear after restartCheck Cursor → Settings → MCP shows “universalbench” with a green status dot
401 or 403 errorsURL has a typo. The path after /u/ must match exactly what your dashboard shows
Slow first callCold start. Subsequent calls within the same session are fast