Jenkins
The Jenkins MCP server is the MCP Server plugin on your Jenkins controller. The URL is https://{host}/mcp-server/mcp. There is no OAuth. The Official card uses an API key, which is HTTP Basic auth: the username and an API token, Base64-encoded, with a Basic prefix. It is the Jenkins card with the Official badge. Willow also has a built-in Jenkins connector.
Set up Jenkins
- Install the MCP Server plugin on the controller.
- Sign in as the user the agent should act as. Open the user menu → Security → Add new token, generate a token, and copy it. Jenkins shows it once.
- Encode
username:tokenas Base64. On macOS or Linux:
echo -n "<username>:<token>" | base64
Base64 is not encryption. Anyone who can read the string can recover the token.
Set up Willow
- Go to MCP Servers → + Add MCP server, open the Jenkins card with the Official badge, and click + Use.
- Enter the Jenkins host.
- Keep API key. Paste
Basicfollowed by the Base64 string, for exampleBasic dXNlcm5hbWU6dG9rZW4=. - Click Check connection. Assign groups and Publish.
Everyone who uses this server shares that Jenkins user's permissions.
Troubleshooting
Jenkins returns 401
Cause: The key is only the token, or it is missing the Basic prefix.
Solution: Paste Basic plus the Base64 of username:token. Do not send the raw token as a bearer token.