CircleCI MCP Server

Created By
CircleCI-Publica year ago
A specialized server implementation for the Model Context Protocol (MCP) designed to integrate with CircleCI's development workflow. This project serves as a bridge between CircleCI's infrastructure and the Model Context Protocol, enabling enhanced AI-powered development experiences.
Overview

What is CircleCI MCP Server?

CircleCI MCP Server is a specialized server implementation for the Model Context Protocol (MCP) designed to integrate with CircleCI's development workflow, serving as a bridge between CircleCI's infrastructure and the Model Context Protocol for enhanced AI-powered development experiences.

How to use CircleCI MCP Server?

To use the CircleCI MCP Server, you need to configure it in your Cursor IDE by adding the MCP server details to your configuration file and providing your CircleCI API token.

Key features of CircleCI MCP Server?

  • Retrieves detailed failure logs from CircleCI builds.
  • Supports both CircleCI URLs and local project context for log retrieval.
  • Provides formatted logs including job names, execution details, and failure messages.

Use cases of CircleCI MCP Server?

  1. Debugging failed builds by accessing detailed logs.
  2. Analyzing test failures to improve code quality.
  3. Investigating deployment issues quickly without leaving the IDE.

FAQ from CircleCI MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized protocol for managing context between large language models and external systems.

  • Do I need a CircleCI API token?

Yes, a CircleCI API token is required to access your CircleCI projects.

  • Is the package published on npm?

No, the package is not yet published to npm, but installation instructions will be provided once it is.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CircleCI-Public
Star
42
Language
TypeScript
License
Apache-2.0 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)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago