What prerequisites are needed to run the server?
Node.js v14 or later, an AWS account with CodePipeline access, AWS credentials with permissions for CodePipeline and CloudWatch (for metrics), and the Windsurf IDE with Cascade AI assistant.
@cuongdev
Basic information
This is a Model Context Protocol (MCP) server that integrates with AWS CodePipeline, allowing you to manage your pipelines through Windsurf and Cascade. The server provides a standardized interface for interacting with AWS CodePipeline services.
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
This is a Model Context Protocol (MCP) server that integrates with AWS CodePipeline, allowing you to manage your pipelines through Windsurf and Cascade. It provides a standardized interface for interacting with AWS CodePipeline services, enabling natural language control of pipeline operations.
Clone the repository, install dependencies with npm install, and configure the .env file with your AWS region and credentials (using AWS profile, SSO, static keys, or IAM role). Build with npm run build, start with npm start, and add the server configuration to your Windsurf MCP config file at ~/.codeium/windsurf/mcp_config.json. Once configured, Cascade can interpret natural language requests like "List all my pipelines" or "Trigger the 'test-build' pipeline".
Node.js v14 or later, an AWS account with CodePipeline access, AWS credentials with permissions for CodePipeline and CloudWatch (for metrics), and the Windsurf IDE with Cascade AI assistant.
You can use an AWS profile (recommended for local dev), AWS SSO, static access keys in the `.env` file, or an IAM role if running on EC2/ECS/Lambda/EKS. Set `AWS_PROFILE` and `AWS_REGION` in `.env` or in the Windsurf MCP `env` block.
Add a server entry to `~/.codeium/windsurf/mcp_config.json` using the `command` and `args` pointing to the built `dist/index.js`, and set the required AWS environment variables. Then restart Windsurf.
You can list pipelines, get pipeline state and details, list and trigger executions, approve/reject manual approvals, retry failed stages, view execution logs, stop executions, tag resources, create webhooks, and get pipeline metrics.
Ensure the server is running, check AWS credentials (verify with `aws sts get-caller-identity`), confirm the `mcp_config.json` file format is correct, and restart Windsurf after making changes. Use `DEBUG=* npm start` for verbose logging.

Model Context Protocol Servers
Development environments for coding agents. Enable multiple agents to work safely and independently with your preferred stack.
Model Context Protocol (MCP) server for Kubernetes and OpenShift
MCP Server for kubernetes management commands

Nippy is drag-and-drop hosting (nippy.host) with an MCP server: connect it and your assistant can publish HTML, folders of photos, or file downloads to a live *.nippy.site URL — and keep editing the site in place at the
Comments