ToolMCP

MCP config generator

Describe the servers once; get the file the client actually reads — a project .mcp.json, the claude mcp add commands, Claude Desktop’s claude_desktop_config.json, or Cursor’s .cursor/mcp.json. It all happens in this page: no upload, no account, tokens included.

The generator needs JavaScript. Without it the form still shows what each field is for, and the example below is a working project .mcp.json you can adapt by hand.

Target

Where the config goes

A project .mcp.json is committed and shared with your team.

Servers

1 server

Add from a preset

01 Server

Name

The key in the config, and the prefix on its tools.

Transport

Command

Arguments

One per line.

Environment

KEY=VALUE, one per line.

Claude Code expands ${VAR} and ${VAR:-default} in .mcp.json — in command, args, env, url and headers — so a shared file can point at a secret each teammate holds in their own environment. Other clients do not.

Output

{
  "mcpServers": {
    "filesystem": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/your/project"
      ]
    }
  }
}

save as .mcp.json in your project root

Then check it

claude mcp list

Claude Code asks you to approve each server from a project .mcp.json the first time. claude mcp get <name> shows one server’s status.

How the files relate

Claude Code has three MCP scopes, and the same server name can be defined in more than one of them. It connects once, using the entry from the highest-precedence source — the whole entry, not a merge of the fields.

01 Local — the default Stored in ~/.claude.json under that project’s path, so it loads in that project only and stays private to you. This is what claude mcp add writes when you pass no --scope. highest
02 Project — .mcp.json A file at the project root, meant for version control. Claude Code prompts for approval before it uses a server from this file in an interactive session; claude mcp reset-project-choices clears those answers. shared
03 User — every project Also stored in ~/.claude.json, at the top level rather than under a project. Added with --scope user, private to your account, available in all your projects. lowest

Other clients read their own files. Claude Desktop reads claude_desktop_config.json — on macOS ~/Library/Application Support/Claude/, on Windows %APPDATA%\Claude\ — and the documented shape there is a local command/args/env server. A remote server is added in the app instead: Settings → Connectors → Add custom connector. Cursor reads .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project, and its examples carry no type key.

A url needs a type in Claude Code. An entry with no type is read as a stdio server, so a URL entry copied from another client’s docs fails until you add "type": "http" (or "sse" / "ws"). In JSON, streamable-http is accepted as an alias for http.

Sources: Claude Code · MCP · MCP · connect local servers · MCP · connect remote servers · Cursor · MCP

Guides that use these files

All tools · Everything on MCP