jenkins-slack-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| login_jenkinsB | Login to Jenkins. Opens browser to Jenkins token page for new users. Validates credentials and auto-discovers all jobs. |
| login_slackA | Login to Slack via OAuth. Opens browser for authorization. Requires SLACK_CLIENT_ID and SLACK_CLIENT_SECRET env vars. |
| statusA | Check current login status for Jenkins and Slack |
| list_jobsA | List all available Jenkins jobs in table format with status. Supports filtering by name. |
| job_detailsA | Get build parameters for a specific Jenkins job in table format. |
| trigger_buildB | Trigger a Jenkins build with parameters. Sends Slack DM if configured. |
| refresh_jobsA | Re-fetch all jobs from Jenkins (use after new jobs are created) |
| stop_buildB | Stop/cancel a running Jenkins build. |
| build_statusA | Get the status of a specific build or the latest build of a job. Shows build number, status, duration, displayName, and description. |
| build_consoleA | Get console output (last 100 lines) of a specific build or the latest build. |
| build_historyA | Get recent build history for a job. Shows last N builds with status, duration, and timestamps. |
| whoamiA | Get current Jenkins and Slack user details |
| logoutA | Clear all stored credentials and jobs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have clear, distinct purposes (trigger, list, stop, status, console, history). The only minor overlap is between 'status' and 'whoami', which both reveal login state but differ in detail (login check vs. user information).
Tool names follow a consistent snake_case verb_noun pattern (e.g., trigger_build, list_jobs, stop_build). Even the bare verbs (status, whoami, logout) are standard, predictable names for their actions.
13 tools is well within the ideal range for a Jenkins+Slack integration. Each tool covers a distinct aspect of the workflow—authentication, job discovery, build control, and monitoring—without unnecessary bloat.
The tool surface covers the full lifecycle for this domain: login/logout, job listing/details, triggering and stopping builds, status checks, console output, and history. The Slack integration is minimal but purposeful (DM on trigger), and no critical operations are missing.