{"id":"jenkinsci-mcp-server-plugin","name":"mcp-server-plugin","af_score":55.2,"security_score":46.2,"reliability_score":22.5,"what_it_does":"Provides a server-side MCP (Model Context Protocol) interface for Jenkins, exposing Jenkins jobs/builds and related operations as MCP tools via multiple HTTP-based transport endpoints (SSE, streamable HTTP, and stateless HTTP).","best_when":"You operate Jenkins internally (or behind a gateway/VPN) and want MCP clients to interact with Jenkins tools over HTTP transports.","avoid_when":"You cannot protect Jenkins API tokens/credentials or cannot control origins/headers (the plugin allows optionally relaxing Origin validation), or you need strict rate-limit/usage guarantees that are not documented for the MCP layer.","last_evaluated":"2026-03-30T13:52:23.732688+00:00","has_mcp":true,"has_api":false,"auth_methods":["HTTP Basic Authentication with Jenkins API token"],"has_free_tier":false,"known_gotchas":["Some MCP transports may have client compatibility quirks (README notes Copilot does not work well with streamable transport; suggests using SSE).","Stateless vs session-based transports can affect how clients manage connections and state.","Origin header validation is not enforced by default; if a client does not send Origin, deployments that enable strict Origin validation may reject requests.","Large log retrieval is limited via a system property (BuildLogsExtension.limit.max); agents should be prepared for truncated/limited logs."],"error_quality":0.0}