# CircleCI MCP for AI Agents AI Agent Connect > CircleCI MCP lets you manage CI/CD pipelines through your AI agent. You can trigger builds, check job statuses, and audit workflows without switching tabs. It connects your CircleCI account to your agent so you can handle deployment tasks using natural language. ## Overview - **Category:** ship-it - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_RYNFniMxh53CKeYToBM2UNUbXRz4n2cftwtxDiON/ai-agent-connect - **Tags:** continuous-integration, continuous-deployment, pipeline-automation, build-automation, workflow-orchestration, software-delivery ## Description You can connect your CircleCI account to your AI agent to handle your CI/CD pipelines using natural conversation. This Connector lets you manage how you monitor and trigger automated builds without jumping back and forth between your code and the CircleCI dashboard. Instead of hunting for specific project IDs or digging through nested menus to find a failed job, you can just ask your agent for the status. It pulls the data and puts it right in front of you. You can also handle the repetitive stuff, like triggering a new pipeline run for a specific branch or checking which shared contexts are active for a project. It makes the whole software delivery loop feel like a conversation rather than a series of clicks. Because Vinkius hosts this, you can plug it right into your existing setup and start using it immediately. Instead of being a tab-jumper, you become a conductor, staying in your workspace while the agent handles the heavy lifting of navigating the CircleCI infrastructure. ## Tools ### get_my_cci_profile Get your account details and membership info. This helps you confirm which user is currently authenticated. ### get_workflow_details Pull specific data for a single workflow. Use this to see the structure of a specific pipeline. ### list_cci_contexts See all shared contexts for an organization. This is useful for checking available environment variables. ### list_workflow_jobs See every job inside a specific workflow. Use this to audit the full sequence of a build. ### list_cci_pipelines List your most recent CI/CD pipelines. This gives you a quick look at recent activity across projects. ### trigger_cci_pipeline Start a new pipeline run for a project. You can use this to kick off builds on specific branches. ### get_job_details Get the execution status and metadata for a specific job. This helps you find exactly where a build failed. ### list_pipeline_workflows List all workflows tied to a specific pipeline. This helps you see the different paths a pipeline can take. ## Prompt Examples **Prompt:** ``` Show me the status of the last 3 pipelines for the 'api' project. ``` **Response:** ``` ### Recent Pipelines for 'api' | Pipeline ID | Branch | Status | | :--- | :--- | :--- | | `550e8400` | `main` | **Success** ✅ | `440e8400` | `main` | **Failed** ❌ | `330e8400` | `dev` | **Success** ✅ Would you like to see the logs for the failed run? ``` **Prompt:** ``` Trigger a new build for the 'frontend' project on the 'staging' branch. ``` **Response:** ``` 🚀 **Triggering build...** I've started a new pipeline for the **frontend** project on the **staging** branch. * **Status:** Started * **Pipeline ID:** `770e8400-e29b-41d4-a716-446655440000` I'll keep an eye on it for you. ``` **Prompt:** ``` What's the status of the 'deploy' job in workflow wf-999? ``` **Response:** ``` Checking workflow `wf-999`... * **Job Name:** `deploy` * **Status:** **On Hold** ⏳ * **Reason:** Waiting for manual approval from a release manager. Would you like me to trigger the next step? ``` ## Capabilities ### Trigger new pipeline runs Start a new build for a specific project and branch using a simple text command. ### Check recent pipeline history Get a list of the latest CI/CD activities across your projects. ### Audit specific job status Pull metadata and execution states for individual jobs to find where things broke. ### View workflow structures See the list of jobs and details for specific workflows within your pipelines. ### Manage shared contexts List and check the shared environment contexts used for your organization. ### Retrieve user profiles Get your own user profile and membership information directly from the account. ## Use Cases ### Debugging a failed build A developer asks why the last build failed. The agent pulls the job metadata and points out the specific error in the logs. ### Manual production deployment A release manager tells the agent to start a build on the main branch. The agent triggers the pipeline and confirms the ID. ### Onboarding and permissions A new team member asks for their account details. The agent retrieves their profile and organization membership info. ### Environment audit A security lead wants to see which contexts are shared. The agent lists all active organization contexts for review. ## Benefits - Stop switching tabs by checking the status of your latest builds directly in your chat window. - Kick off new production builds on specific branches instantly without navigating the web dashboard. - Identify exactly where a build failed by pulling detailed job metadata with a single question. - Audit your shared environment variables and contexts to ensure your secrets are properly managed. - Get a full view of your workflow sequence to understand how jobs are sequenced across your projects. ## How It Works The bottom line is you get direct, conversational control over your CircleCI builds without leaving your primary workspace. 1. Subscribe to the CircleCI MCP on the Vinkius Marketplace. 2. Add your CircleCI Personal API Token to the Connector configuration. 3. Ask your AI agent to trigger builds, check statuses, or audit workflows. ## Frequently Asked Questions **Can I use the CircleCI MCP to trigger builds?** Yes. You can ask your agent to start a new pipeline for any project and branch. It will handle the request and return the new pipeline ID for you. **How do I see why my build failed using this Connector?** Just ask your agent for the status of a specific job. It will pull the execution metadata and tell you exactly where the process stopped. **Does the CircleCI MCP work with Cursor and Claude?** Yes. Since it's an Connector, it works with any compatible client like Claude, Cursor, Windsurf, or VS Code once connected via Vinkius. **Can I check my user profile with CircleCI MCP?** Yes. Your agent can retrieve your account details, membership information, and other profile data directly from CircleCI. **Can I see all the jobs in a specific workflow?** Yes. You can ask your agent to list all jobs within a workflow. It will show you every step in the sequence and their current statuses. **Can I manage shared contexts with CircleCI MCP?** Yes. You can ask your agent to list the shared contexts for your organization to see what environment variables are currently available. **Can I trigger a build for a specific branch through the agent?** Yes! Use the `trigger_cci_pipeline` tool. You need to provide the project slug (e.g., `gh/org/repo`) and the branch name. The agent will instruct CircleCI to start the pipeline immediately. **How do I see why a specific job failed?** Use the `get_job_details` tool with the project slug and job number. Your agent will fetch the execution status and metadata, which often points to the cause of failure. **Where do I find my CircleCI API Token?** Log in to CircleCI, go to **User Settings -> Personal API Tokens**. You can generate and copy a new token from there.