Overview

Product video
The CircleCI Model Context Protocol (MCP) Server is a specialized docker packaged integration that bridges your CircleCI CI/CD infrastructure with AI powered development tools. Built on the open Model Context Protocol standard, this server enables AI assistants like Amazon Q Developer, Cursor, Claude Code, Windsurf, and VS Code Copilot to interact with your CircleCI pipelines using natural language.
You can:
- Diagnose build failure with all the context in plain language: The CircleCI MCP Server gives agents direct access to build logs and metadata, letting you quickly identify issues with direct questions like: Why did this PR build fail?
- Speed up your feedback loop: Empowered with your code and your build logs, agents will help you fix your error and trigger another build; keeping you/your developers in flow and resolving CI issues faster.
Highlights
- Easy Deployment & Setup: 1. Deploy the docker container from AWS Marketplace 2. Configure environment variables with your CircleCI API token 3. Connect to your AI development tools using MCP protocol 4. Start using natural language to interact with your CI/CD pipelines
- What's Included: 1. Pre-built docker image with CircleCI MCP server 2. Comprehensive documentation and setup guides 3. Example configurations for popular IDEs
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Vendor refund policy
No refunds provided. For inquiries, please contact AWS-Marketplace@circleci.comÂ
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Docker Container for CircleCI MCP Server
- Amazon Bedrock AgentCore
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
CircleCI MCP Server
Additional details
Usage instructions
Select the appropriate version of our MCP Server in AWS Marketplace, then navigate to the AI agent platform to host this agent.
On configure agent page, set the following environment variables
- CIRCLECI_TOKEN=<YOUR_CIRCLECI_API_TOKEN>
- start=remote
CircleCI Personal API Token - you can generate one through CircleCI.
- Learn more: https://circleci.com/docs/managing-api-tokens/Â
- Quick Access: https://app.circleci.com/settings/user/tokensÂ
IDE Integration made simple https://github.com/CircleCI-Public/mcp-server-circleci?tab=readme-ov-file#circleci-mcp-serverÂ
CircleCI server: https://circleci.com/mcp/Â
CircleCI server natural language CI for AI driven workflows https://circleci.com/blog/circleci-mcp-server/Â
Resources
Support
Vendor support
Get support - https://support.circleci.com/hc/en-us Support docs - https://circleci.com/docs/ AWS infrastructure support -
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products



Customer reviews
Automated CI/CD pipelines have transformed deployment speed and collaboration for my teams
What is our primary use case?
I have been using CircleCIÂ for over three years as part of my DevOps toolchain.
I use CircleCI to automate CI/CD pipelines, including build, test, and deployment workflows across multiple applications. In one pipeline, I deploy an application to my Kubernetes cluster on AWS in the cloud, and I use CircleCI to automate that deployment in the form of a pipeline.
CircleCI is helping me automate my deployment workflows effectively, and it is a fit use case for the same. I have been using it for many application deployments, and it is working for end-to-end deployment.
What is most valuable?
CircleCI offers fast parallel builds, easy integration with GitHub , and the ability to deploy applications on Kubernetes pods, which are amazing features.
Fast parallel builds and GitHub integration have definitely helped my team reach faster time to market for our applications. Previously, our deployment used to take a couple of hours when doing it manually, but with CircleCI pipeline, our hours-long job has been converted to a couple of minutes.
Its simplicity, fast pipeline execution, and strong GitHub and GitLab integrations are definitely unique advantages I discovered while using CircleCI.
Time saved is one of the key aspects I have seen since using CircleCI. I have noticed fewer deployment errors, and it has helped me with easy debugging. Time saved is directly proportional to the cost and effort saved.
CircleCI has positively impacted my organization by integrating directly with my Git repositories as a fully managed SaaS platform.
CircleCI has a great impact on my team's collaboration and communication, with around 25 to 40 developers and DevOps engineers using it daily across multiple repositories and environments, helping us use it at scale.
CircleCI has significantly increased our release frequency and deployment speed compared to before I started using it.
CircleCI improves security for my organization by enforcing automated checks in the pipeline and securely managing secrets through environment variables while providing auditable deployments.
CircleCI integrates seamlessly with my DevOps toolchain by connecting directly to GitHub, container registries, and my cloud platform AWSÂ , allowing the entire CI/CD flow from code commit to deployment and monitoring with minimal manual effort.
What needs improvement?
I believe debugging complex pipelines and managing credits can sometimes be challenging, especially for large workflows, so these areas can be improved.
The user interface can definitely be improved to debug complex pipelines. I would benefit from better AI-generated insights where I can debug the pipelines easily without going through detailed logging.
For how long have I used the solution?
I have been working in my current field for more than 10 years.
What do I think about the stability of the solution?
CircleCI has been very stable in my experience with consistent pipeline executions and minimal platform-related issues.
What do I think about the scalability of the solution?
CircleCI scales well as my team and repositories grow, allowing me to run multiple concurrent pipelines without performance degradation.
I have not encountered any limitations with CircleCI's scalability as my projects have grown. However, managing pipeline complexity and optimizing credits usage required additional planning, which was manageable.
How are customer service and support?
CircleCI team has been responsive and knowledgeable whenever I sought assistance.
How would you rate customer service and support?
Negative
Which solution did I use previously and why did I switch?
Previously, I used Jenkins but moved to CircleCI to reduce maintenance overhead and simplify pipeline management, as CircleCI provided faster setup, better scalability, and a more streamlined developer experience.
How was the initial setup?
CircleCI documentation is generally clear and well-structured, making it easy to get started and implement standard CI/CD workflows.
What was our ROI?
CircleCI has significantly reduced build and deployment times, saving substantial engineering hours and effort for me, which has directly improved my productivity and release velocity, reflecting incredible ROI.
What's my experience with pricing, setup cost, and licensing?
My experience with CircleCI's pricing model is quite straightforward with no upfront setup cost, and the licensing is flexible based on my usage. Costs can increase as pipeline usage scales, but they remain predictable and manageable with proper monitoring.
Which other solutions did I evaluate?
Before choosing CircleCI, I evaluated Jenkins , GitHub Actions , and GitLab CI/CD. CircleCI stood out due to its ease of use, faster execution, and lower operational overhead.
What other advice do I have?
CircleCI has been a reliable and efficient platform for me that has helped streamline my delivery process and CI/CD process. With continued enhancements around cost visibility and advanced pipeline management, it can deliver even greater value.
My advice for others looking into using CircleCI is to invest time in pipeline design and cost monitoring early to get the best long-term value from the platform. CircleCI would be a strong choice for those who want fast, reliable CI/CD with minimal operational overhead.
I would rate this review an 8 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Intuitive, Easy, and Effective for CI/CD
Automated deployments have streamlined cloud releases but configuration orbs still need simplification
What is our primary use case?
CircleCI is used primarily as the pipeline for application deployment. When a pull request is created in GitHub , it triggers a CircleCI pipeline because of the GitHub integration. During the CircleCI pipeline, the application goes through building and deployment to the appropriate destination, which can be a Lambda or AKS microservices.
What is most valuable?
CircleCI's GitHub integration is the best feature offered. The GitHub integration is most valuable because of its ease of use, as it only requires integration with the GitHub repository and then creating the pipeline as a YAML file within the repository code.
CircleCI has positively impacted the organization, as it has been used for many years and serves as the main source for application deployment. Every deployment is conducted through CircleCI, and this is what keeps the company functioning.
What needs improvement?
CircleCI's Orbs are not as easy to use as they could be. If CircleCI implemented a function approach similar to GitHub Actions , it would be significantly better.
CircleCI could be improved if it could function without Orbs. Instead of Orbs, using a function approach like GitHub Actions would be beneficial.
For how long have I used the solution?
CircleCI has been used for two years.
What do I think about the stability of the solution?
CircleCI is stable.
What do I think about the scalability of the solution?
CircleCI's scalability is easier to manage, but it comes at a high cost.
How are customer service and support?
A customer support ticket has never been opened.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
This company already had CircleCI running for several years before starting at this position.
How was the initial setup?
CircleCI was purchased through the AWS Marketplace .
What about the implementation team?
The company does not have a business relationship with this vendor beyond being a customer.
What was our ROI?
A return on investment with CircleCI has not been observed, and no relevant metrics such as time saved or fewer employees needed can be shared.
What's my experience with pricing, setup cost, and licensing?
There is not much experience with pricing, setup cost, and licensing because that is managed by the legal team.
Which other solutions did I evaluate?
Other options were not evaluated before choosing CircleCI, but after choosing CircleCI, GitHub Actions and Harness are already being evaluated.
What other advice do I have?
For others looking into using CircleCI, study thoroughly about CircleCI's Orbs because they are quite complicated. The overall review rating for CircleCI is 6 out of 10.