evergreen-mcp-server
Verified Safeby evergreen-ci
Overview
Enables AI assistants to interact with the Evergreen CI/CD platform for build analysis, project management, and debugging.
Installation
docker run --rm -i -v ${HOME}/.kanopy/token-oidclogin.json:/home/evergreen/.kanopy/token-oidclogin.json:ro -v ${HOME}/.evergreen.yml:/home/evergreen/.evergreen.yml:ro ghcr.io/evergreen-ci/evergreen-mcp-server:latestEnvironment Variables
- EVERGREEN_USER
- EVERGREEN_API_KEY
- EVERGREEN_TOKEN_FILE
- EVERGREEN_PROJECT
- WORKSPACE_PATH
- EVERGREEN_MCP_TRANSPORT
- EVERGREEN_MCP_HOST
- EVERGREEN_MCP_PORT
Security Notes
The server loads authentication credentials (OIDC tokens or API keys) from local files (`~/.evergreen.yml`, `~/.kanopy/token-oidclogin.json`) or environment variables, which relies on the host system's security. It uses `pyjwt.decode` with `verify_signature=False` for extracting user ID from access tokens; however, this is explicitly commented as being for display/query purposes only, with actual authentication verification handled by the OIDC provider during token exchange. This is a justified, but notable, design decision.
Similar Servers
context-portal
Manages structured project context for AI assistants and developer tools, enabling Retrieval Augmented Generation (RAG) and prompt caching within IDEs.
mcp-servers
A curated collection of Model Context Protocol (MCP) server configurations to integrate various developer tools and services with AI agents.
buildkite-mcp-server
An MCP server that exposes Buildkite CI/CD data (pipelines, builds, jobs, tests) to AI tooling and editors for enhanced context and automation.
openapi-mcp-server
Converts OpenAPI specifications into Model Context Protocol (MCP) tools, enabling AI assistants to interact with APIs.