Skip to main content
Claude Desktop has supported MCP since late 2024. UniversalBench connects in one config edit with no headers to configure.

Setup

1

Get your personal MCP URL

Sign up at universalbench.dev. After email verification, copy your URL from the dashboard.
2

Open the config file

On macOS: ~/Library/Application Support/Claude/claude_desktop_config.jsonOn Windows: %APPDATA%\Claude\claude_desktop_config.jsonCreate the file if it does not exist.
3

Add UniversalBench

That is the entire config. One URL, no headers field. Claude Desktop reads the URL on startup and the tools appear.
4

Restart Claude Desktop

Quit fully (not just close the window) and reopen. UniversalBench appears in the conversation tool list.

What you can do now

Claude Desktop is great for ad hoc analysis. Try:
Use UniversalBench to search the web for the largest pension fund returns in 2026, pull the numbers, and analyze the top 10.
Claude Desktop calls web_search for current data, runs Python to parse and analyze, and returns clean analysis. Or:
Store my Stripe API key in UniversalBench’s secrets vault under the name STRIPE_KEY. From now on, whenever I ask you to do anything with payments, inject it by name.
Claude uses secrets_vault to store the value encrypted. On every subsequent payment task, it injects the secret by name without pasting the value into the conversation.

Tips

Claude Desktop persists conversations but loses tool state between calls. UniversalBench’s session_id solves this when you want a Python variable, imported module, or loaded dataframe to survive multiple tool calls in a long conversation.

Troubleshooting

ProblemFix
Tools do not appearOpen Developer then MCP Logs in Claude Desktop and read the connection error
Config file path wrongThe path is OS specific. See Step 2 above
401 or 403 errorsRe copy the URL from your dashboard. One wrong character in the token breaks auth
URL stopped working after rotationUpdate the config with the new URL from your dashboard