Watch: set up mcp servers
No sound. Each step is captioned on screen and also written out in the guide below.
AI Tools
Write MCP server configs for Claude Code, Claude Desktop, Cursor, VS Code, and Codex, check the one you have, and find servers in the official MCP Registry.
Paste .mcp.json, claude_desktop_config.json, .cursor/mcp.json, .vscode/mcp.json, or the [mcp_servers] part of ~/.codex/config.toml.
The server list loads when you open this tab.
No sound. Each step is captioned on screen and also written out in the guide below.
Claude Code, Claude Desktop, Cursor, VS Code, or Codex. Each reads a slightly different file.
Find one in the registry, or enter its command or URL yourself.
Paste it into the file shown, or run the terminal command, then restart the app.
servers vs mcpServers, a missing type.command, npx without -y, relative paths.${env:NAME} where the app expects ${NAME}, and the reverse.No. Configs are built and checked in your browser. The registry list is a copy kept on bytesbench.com, so searching it doesn't send anything to another site.
They read the same idea in slightly different shapes. VS Code lists servers under servers and needs a type; Claude Code, Claude Desktop, and Cursor use mcpServers; Codex uses TOML. They also refer to environment variables differently: ${NAME} in Claude Code, ${env:NAME} in Cursor, and ${input:id} prompts in VS Code.
Keep them out of files you share or commit. With "Read secrets from environment variables" on, the config refers to a variable and you set the key in your environment. VS Code asks for it and stores it securely instead. Claude Desktop can't read variables, so keep its file private.
The official MCP Registry lists servers published by their authors; it doesn't review their code. A local server runs with your permissions, so check its source and publisher before adding it. Package versions are pinned, so what you checked is what runs.
It's a copy of the official MCP Registry, refreshed regularly. The date is shown above the list.