Generate and install the configuration

Open the MCP Config Generator. Choose your host and the stdio transport.

Enter a short server name, the command, and each command argument. Use an absolute path for the disposable practice folder.

If the server needs a credential, enter only the environment-variable name. The generator deliberately uses a placeholder instead of collecting the value.

Copy the JSON to the configuration location documented by your host. Restart or reload the host so it reads the new server.

Validate the generated shape before installation:

• the server name is unique and recognizable
• command and arguments are separate values
• the package version is pinned when appropriate
• the practice path is absolute and narrow
• no secret value appears in JSON
• the selected transport matches the server

Make a backup of the working host configuration. Add only this server, reload, and inspect the host’s diagnostics. If the whole configuration fails to parse, restore the backup rather than making several speculative edits.

Confirm that the server appears by name and that its advertised capabilities match what you expected.

Discovery is part of installation verification. A process that starts but advertises an unexpected write tool or broader resource scope has not passed review. Disable it and investigate the exact installed version.

Configuration controls how the host launches the server; it does not sandbox the process by itself. Keep using a disposable folder and harmless data for the first call.

Save the sanitized configuration and the expected capability list. You can compare them after an upgrade instead of relying on memory.