Developer ToolsFree generatorPDF, Excel, Word export

claude_desktop_config.json Generator for MCP Servers

Claude Desktop reads a JSON file that lists the local MCP servers to launch. A missing comma or a single backslash on Windows is enough to stop a server from loading. This generator produces a clean mcpServers entry you can paste in.

Fill in

Server name (key)

Command

Script or package

On Windows, double every backslash in JSON.

Extra argument

ERP base URL

Secret environment variable name

Secret placeholder

Generated code

Download:

claude_desktop_config.json

{
  "mcpServers": {
    "erp-readonly": {
      "command": "node",
      "args": [
        "C:\\mcp\\erp-server\\dist\\index.js",
        "--read-only"
      ],
      "env": {
        "ERP_BASE_URL": "https://erp.example.com/api",
        "ERP_API_TOKEN": "REPLACE_WITH_SERVICE_TOKEN"
      }
    }
  }
}

Where the file lives

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Fully quit and reopen Claude Desktop after editing. Open the developer settings to read the server logs if the server does not appear.

If the file already has an mcpServers object, add your entry beside the existing ones instead of pasting a second mcpServers key. Never commit real tokens. Use a least-privilege service account for the env value. Verify the file path and options against the current Claude Desktop documentation for your version.

Roll out MCP to my ERP team

Optional: we can help design a read-only ERP MCP server and a safe rollout plan.

Optional. The tool and every export work without this. No spam.

How to use it

Enter a short server name, choose how the server starts (node, python, npx, uvx or docker), give the script or package, and add any arguments. Put the ERP base URL and a service token in the env section, not on the command line, so they are not visible in process listings. Copy the output into your config file, keeping valid JSON, then restart the app fully, not just close the window.

Use a dedicated read-only ERP service account
Double backslashes in Windows paths
Keep one entry per server and unique names

What each key does

The mcpServers object maps a name to a launch definition. Command is the executable, args is the list of arguments passed to it, and env adds environment variables to the child process. Desktop starts the process and speaks MCP over standard input and output. That is why the server must write protocol messages only to stdout and logs to stderr, otherwise the handshake breaks.

Reading the result and debugging

After a restart, your tools should appear in the tools menu. If not, check three things in order: the JSON parses (paste it into any validator), the command resolves on the PATH Desktop sees (node or npx installed for all users), and the server starts by itself in a terminal without errors. Log files in the Claude logs folder show the launch error and the stderr output from your server.

Common mistakes

Frequent problems include smart quotes pasted from documents, trailing commas, relative script paths, relying on a shell profile for PATH, and storing production admin credentials in the file. Remember the file is plain text on the user's machine. For shared or regulated environments, prefer a remote server with proper authentication over distributing secrets to laptops.

Frequently Asked Questions

Where is claude_desktop_config.json on Windows?

It is normally under %APPDATA%\Claude\ in a file named claude_desktop_config.json. You can also open it from the developer section of the Claude Desktop settings, which creates it if it does not exist yet.

Why does my server not show up?

Most often the JSON is invalid, the command is not on the PATH, or the server crashes at start. Run the same command in a terminal first, then check the Claude Desktop log files for stderr output.

Can I put secrets in the env block?

You can, and it is common for local use, but the file is plain text. Use a least-privilege service account, restrict file permissions, and avoid reusing a personal admin token.

Does this work for remote MCP servers?

This file launches local processes. Remote servers are generally added through the connectors or integrations settings rather than a command entry, so check the current product documentation for your plan.

If you need MCP access to your ERP rolled out safely across a team, Netray can design the server, the roles and the deployment with you.

Talk to an Expert Explore More Free Tools

Related Tools

Developer Tools

More Developer Tools tools

See all

Back to All Tools