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 container builds have accelerated our Go deployments and simplified AWS workflows
What is our primary use case?
My main use case for CircleCI involves different CI capabilities, mostly building containers and general applications. I use CircleCI for building containers and applications, specifically for our GoLang application. We have an ECS application written in GoLang which runs scans against the infrastructure. Regardless, it is completely built and managed. The configs are also stored in Bitbucket , and CircleCI is connected to it, running all the builds, processes, and deployment in the end to the ECS.
What is most valuable?
The best features CircleCI offers are probably the modules, which have great extendability. I use the modules or extendability in CircleCI primarily for classic pushes to AWS , and those include registry sign-ons and other cases.
CircleCI has positively impacted my organization by allowing us to build quicker and do things quicker. It does the job really well. These extensions are called Workflows. I have used some AWS Workflows, and there are multiple others.
CircleCI helps you build and do things quicker. It is difficult to say if there were specific improvements, but there is general reliability and probably improvements overall.
What needs improvement?
I have no idea how CircleCI can be improved. I am a user, not a developer of CI tools. I do not really have anything to add about the needed improvements, even small things that could make my experience better.
For how long have I used the solution?
I have been using CircleCI for around a year.
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 great. I have never had any problems with it.
How are customer service and support?
I did not deal with CircleCI's customer support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I previously used multiple solutions. The very first one was GitLab , but it was just an experiment, because there are quite a few limitations that we had with GitLab , so we had to switch.
What was our ROI?
I cannot say if I have seen a return on investment. It is very difficult to tell.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that I only used CircleCI on the free tier.
Which other solutions did I evaluate?
Before choosing CircleCI, I evaluated other options, specifically Jenkins .
What other advice do I have?
My advice for others looking into using CircleCI is to read more documentation. The documentation is really good. I would rate this review an 8.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automated pipelines have accelerated deployments and dashboards now reveal clear pricing and security gaps
What is our primary use case?
For a specific example of how I use CircleCI for deployments in my projects, I utilize it for continuous integration and automation to have the builds. I create YAML pipelines with it, and we first have some steps such as installing Node if it is a front-end build or installing the dependencies. After that, I build the project. Following the build, I deploy it on AWS Elastic Container Service of the image. After the image is deployed, I deploy that image on the running EC2 , either in EC2 or within the S3 bucket. Then, the environment is ready, and I run the tests against that environment.
Additionally, I use CircleCI for insights and dashboards, doing some dashboarding and monitoring the results, duration, and how the runs have been, including the output and generation of reports or sending notifications to email addresses. I also connect it with Azure DevOps and GitHub .
What is most valuable?
Among those features, I find the most valuable in my day-to-day work the automation aspect, as we have a large product team with many developers who continuously create branches and push code, necessitating automation that builds the pipeline and the branches automatically while giving faster feedback. There is speed, flexibility, and intelligent pipeline orchestration possible with CircleCI, which we appreciate. Additionally, we have hooks and can run tasks on commit or push, which allows executions based on those events, and the self-hosted runners to run jobs on our infrastructure or use provided agents by CircleCI itself are also beneficial.
CircleCI has positively impacted my organization by bringing in faster deployments, which means we can release faster, receive quicker feedback, and enhance collaboration and communication across the entire team. We benefit from really good dashboards, build performance analytics, and optimization of resources, which allows for multiple containers or virtual machines, significantly reducing build time. Additionally, the security and vulnerability scanning provided out of the box helps tremendously, as we just need to push the code and everything is managed by our CircleCI YAML scripts.
What needs improvement?
I believe CircleCI should leverage the growing trend of AI by offering an out-of-the-box AI-driven dynamic YAML file creation feature using natural language processing. Instead of having users define pipelines manually, users could simply use natural language to define their needs and let the AI generate the YAML configuration automatically. Implementing a multi-agent architecture could also enhance usability.
I rated CircleCI six out of ten because I think they need more transparency in pricing, as there are instances of unclear network data transfer and storage costs related to caching and workspaces. Additionally, there are sporadic platform security incidents that need addressing, and pipelines require good protection. Secret rotation should also be prioritized. There are occasionally long-running workflows that can be difficult to debug, and improvements could be made in job startup times and cache management.
For how long have I used the solution?
How was the initial setup?
What other advice do I have?
To ensure that security and compliance requirements are met while using CircleCI, we utilize restricted contexts for secrets along with short-lived credentials. We follow some regulatory guidelines, ensuring that every job runs in an isolated environment, either in a Docker container or a virtual machine. Furthermore, we maintain secret rotation and use secure API tokens while implementing appropriate access controls.
I rate this product six out of ten.
Fast, User-Friendly, but Keep an Eye on Costs
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.