Skip to content

allow setting env values for individual mcps #81

@garland3

Description

@garland3

For example.

"env": {
"CLOUD_PROFILE": "my-profile-9",
"CLOUD_REGION": "us-east-7"
},

So on the mcp.json.

{
"my-external-tool": {
"command": [
"wrapper-cli",
"my.external.tool@latest",
"--allow-write"
],
"cwd": "backend",
"env": {
"ENV_VAR_1": "",
"ENV_VAR_2": ""
},
"groups": ["users"],
"is_exclusive": false,
"description": "External MCP server for XYZ functionality",
"author": "Team Name",
"short_description": "Access XYZ APIs via external MCP server",
"help_email": "support@example.com",
"compliance_level": "Public",
"require_approval": [],
"allow_edit": []
}
}

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions