MCP Jenkins Server

Created By
walidcda year ago
Overview

what is MCP Jenkins Server?

MCP Jenkins Server is a Model Context Protocol (MCP) server that provides integration tools for Jenkins, allowing users to interact with their Jenkins server programmatically.

how to use MCP Jenkins Server?

To use the MCP Jenkins Server, clone the repository, install the required dependencies, and configure your Jenkins credentials in a .env file. You can then run the server and use the provided CLI tools to interact with Jenkins.

key features of MCP Jenkins Server?

  • Retrieve Jenkins server information
  • List and inspect Jenkins jobs
  • Access recent builds and their summaries
  • Get detailed build information and console output
  • Manage Jenkins views
  • Trigger job builds with parameters

use cases of MCP Jenkins Server?

  1. Automating Jenkins job management
  2. Monitoring build statuses and outputs
  3. Integrating Jenkins with other tools and workflows

FAQ from MCP Jenkins Server?

  • What are the requirements to run MCP Jenkins Server?

You need Python 3.10+, a Jenkins server with API access, and a Jenkins API token for authentication.

  • How do I configure my Jenkins credentials?

Create a .env file with your Jenkins URL, username, and API token.

  • Can I trigger builds with parameters?

Yes, you can trigger Jenkins job builds with optional parameters.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
walidcd
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago