Configuration builder
Search for the servers you intend to run and add them to the selection. The block below is built from measured values.
Selection (1 of at most 8)
| Cloudinary Asset Management | npx -y sample-mcpRequired secret variables from the raw declaration: CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET · collected on 2026-08-06 Package coordinate: npm:sample-mcp · collected on 2026-08-16 Version the source states: 0.8.11 |
|---|
The file
{
"mcpServers": {
"io-github-subomi-sample-mcp": {
"command": "npx",
"args": [
"-y",
"sample-mcp"
],
"env": {
"CLOUDINARY_API_KEY": "",
"CLOUDINARY_API_SECRET": ""
}
}
}
}
The key per server is its identifier in this registry. The registry does not know the values of environment variables and leaves them empty.
Both are raw declarations from the source and do NOT go into the generated block. The block follows the disclosed start template alone; a version number inside it would be a command nobody has checked.
The start templates
| npm | npx -y {kennung}Package registry npm: invoked through npx with the identifier from the package coordinate. |
|---|---|
| pypi | uvx {kennung}Package registry PyPI: invoked through uvx with the identifier from the package coordinate. |
| oci | docker run -i --rm {kennung}Package registry OCI: invoked through docker run with the image name from the package coordinate. |
Version of the start templates: 1
tracevero · https://tracevero.com/en/werkzeuge/konfiguration