CircleCI MCP Server

Each tool targets a distinct resource or action. The get/list verbs apply to different resources (run, workflow, job, orb, deploy component/environment), and similar-looking tools like get_orb vs get_orb_source are clearly separated by metadata vs source. No two tools appear to do the same thing.

Almost all tools follow the verb_noun pattern (get_*, list_*, cancel_workflow, rerun_workflow, validate_config, download_usage_data). The only exception is 'hello', which breaks the pattern but is a simple connectivity check. This minor deviation prevents a perfect score.

22 tools is on the higher end of the typical range but each tool earns its place given the breadth of CircleCI features covered. The hierarchical read chain (runs → workflows → jobs → logs/tests/artifacts) justifies multiple list/get pairs, and deploy/orb management tools add distinct value. It feels slightly heavy but still reasonable.

The core CI workflow is well-covered: listing and retrieving runs, workflows, jobs, logs, tests, artifacts; cancelling/rerunning workflows; validating config; and orb inspection. A notable gap is the lack of a list_projects tool for discovering available projects, and there are no create/update operations, but for a read/debugging-oriented server this is acceptable.