the IT Hustle
ToolsField ManualAbout

MCP Config Generator

MCP is the ODBC of the AI age — and like ODBC, the hard part is the connection config. Enter your server's command or URL once and get correctly-shaped JSON for Claude Desktop, Claude Code, Cursor, and VS Code.

File: claude_desktop_config.json
{
  "mcpServers": {
    "my-server": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/dir"
      ]
    }
  }
}

Config shapes verified against each client's documented format as of July 2026 — clients evolve, so check their docs if a config is rejected. Everything runs in your browser; nothing you enter is uploaded.

How to Generate an MCP Server Config

Produce correct Model Context Protocol configuration for Claude Desktop, Claude Code, Cursor, or VS Code.

  1. 1
    Pick the transportLocal (stdio) for servers that run as a command on your machine; Remote (HTTP) for servers you reach over a URL.
  2. 2
    Enter the server detailsName the server, then give the command and arguments (stdio) or the URL (HTTP). Add environment variables like API keys one per line.
  3. 3
    Pick your clientSwitch between Claude Desktop, Claude Code, Cursor, and VS Code tabs — each has a slightly different config shape and file location, shown above the output.
  4. 4
    Copy into the right fileCopy the JSON into the file path shown, restart the client, and the server's tools appear. In Claude Code you can also use the `claude mcp add` command instead.

Frequently Asked Questions

The Model Context Protocol is an open standard for connecting AI applications to tools and data sources — think ODBC for AI. An MCP server exposes capabilities (your files, a database, an API) that any MCP-capable client can use without custom integration code.

The protocol is standard but the client config files aren't yet: Claude Desktop and Cursor use an mcpServers object, VS Code uses servers with an explicit type field, and file locations differ. This generator handles those differences so you don't memorize them.

For stdio servers, in the env block — the client passes them to the server process. For HTTP servers, usually as headers. Keys you type here stay in your browser; nothing is uploaded. Never commit config files containing real keys to a shared repo.

Restart the client fully (config is read at startup), check the file path matches the one shown for your client, and for stdio servers run the command manually in a terminal first — if it fails there, it fails in the client too.

Related Tools

Prompt LinterAI Cost PlannerEnv File Manager