Skip to content

Free mcp.json Generator for MCP Servers

Build the config that connects an MCP server to Claude Desktop, Claude Code, Cursor or VS Code: a local command or a remote URL, with env vars and headers.

  • Free, no sign-up
  • Runs in your browser; nothing is uploaded
  • Updated Oct 25, 2026

Environment variables

.mcp.json (project root)

{
  "mcpServers": {
    "my-server": {
      "command": "npx",
      "args": [
        "-y"
      ]
    }
  }
}

Use placeholders for secrets in shared files; never commit real keys.

How to use the mcp.json generator

  1. 1

    Describe the server

    A local command (npx, uvx, docker) or a remote URL.

  2. 2

    Add settings

    Environment variables, arguments or headers.

  3. 3

    Copy for your client

    Each client's file name and format is shown.

What MCP config does

The Model Context Protocol (MCP) lets AI assistants use external tools and data through servers. Each client reads a JSON file listing the servers to start or connect to: Claude Desktop uses claude_desktop_config.json, Claude Code and Cursor use .mcp.json or mcp.json in the project, and VS Code uses .vscode/mcp.json with a servers key.

If your product has an MCP server, publishing a ready config snippet in your docs is the fastest way to get developers to try it.

Questions

Local or remote server?

Local servers run as a command on the user's machine (stdio). Remote servers are reached over HTTP at a URL, often with OAuth or a header token.

Where do secrets go?

In env or headers. Avoid committing real keys to a shared .mcp.json; use placeholders and environment variables.

Why does VS Code use a different key?

VS Code's file uses servers instead of mcpServers. The generator writes the right shape for each client.

Is the config sent anywhere?

No. It is built in your browser.

All free tools

Launch your startup on Aback Launch

Get a launch page that search engines and AI assistants can read, a place in the weekly launch list, and a review by a real person. Free to join.