Add the Jenkins MCP server to VS Code
Config last verified Jun 1, 2026
The exact config to run Jenkins in VS Code — paste it in, restart, and the tools load.
Prerequisites
- VS Code installed.
- MCP_JENKINS_URL — URL of your Jenkins controller. Comma-separated for multiple instances.
- MCP_JENKINS_USER — Jenkins username used to authenticate. Comma-separated to match multiple instances.
- MCP_JENKINS_API_TOKEN — Jenkins API token for the user, generated under your Jenkins account's security settings.
Setup
1. Open .vscode/mcp.json
2. Add this configuration
Add to .vscode/mcp.json
.vscode/mcp.json
json
{
"servers": {
"jenkins": {
"type": "stdio",
"command": "npx",
"args": [
"--yes",
"@kud/mcp-jenkins@latest"
],
"env": {
"MCP_JENKINS_URL": "<MCP_JENKINS_URL>",
"MCP_JENKINS_USER": "<MCP_JENKINS_USER>",
"MCP_JENKINS_API_TOKEN": "<MCP_JENKINS_API_TOKEN>"
}
}
}
}Heads up
- VS Code uses the `servers` key (not `mcpServers`) and requires `type`.
3. Restart VS Code and confirm the Jenkins tools load.
Gotchas
- VS Code uses the `servers` key (not `mcpServers`) and requires `type`.
VS Code is the exception to every other client: its top-level key is "servers", not "mcpServers", and each entry needs an explicit "type" (for example "http" or "stdio"). Secrets are not inlined; instead you declare an "inputs" array and reference each value as ${input:id}, so VS Code prompts for it once and never writes it to disk. Remote servers connect natively with OAuth.