cuongdev/mcp-codepipeline-server

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。原文を見る

5 stars 4 forks 品質 62 トレンド 17

This is a Model Context Protocol (MCP) server that integrates with AWS CodePipeline, allowing you to manage your pipelines through Windsurf and Cascade.

概要

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. - List all pipelines - Get pipeline state and detailed pipeline definitions - List pipeline executions - Approve or reject manual approval actions - Retry failed stages - Trigger pipeline executions - View pipeline execution logs - Stop pipeline executions - Tag pipeline resources - Create webhooks for automatic pipeline triggering - Get pipeline performance metrics - Node.js (v14 or later) - AWS account with CodePipeline access - AWS credentials with permissions for CodePipeline and CloudWatch (read metrics) - Windsurf IDE with Cascade AI assistant 3. Create a .env file based on the .env.example template: 4. Update the .env file with your AWS configuration (see .env.example): : For security, never commit your .

README

以下は原文 README の抜粋です。原文を見る。

AWS CodePipeline MCP Server

Author: Cuong T Nguyen

Features

List all pipelines
Get pipeline state and detailed pipeline definitions
List pipeline executions
Approve or reject manual approval actions
Retry failed stages
Trigger pipeline executions
View pipeline execution logs
Stop pipeline executions
Tag pipeline resources
Create webhooks for automatic pipeline triggering
Get pipeline performance metrics

Prerequisites

Node.js (v14 or later)
AWS account with CodePipeline access
AWS credentials with permissions for CodePipeline and CloudWatch (read metrics)
Windsurf IDE with Cascade AI assistant

Installation

Clone this repository:

git clone https://github.com/cuongdev/mcp-codepipeline-server.git
cd mcp-codepipeline-server

Install dependencies:

npm install

Create a .env file based on the .env.example template:

cp .env.example .env

Update the .env file with your AWS configuration (see .env.example):

AWS_REGION=us-east-1
AWS_PROFILE=your-aws-profile

Note: For security, never commit your .env file to version control.

AWS authentication

You do not need long-lived access keys in .env. Pick one approach:

Approach	Configuration
AWS profile (recommended for local dev)	`AWS_PROFILE=my-profile` — uses `~/.aws/credentials` / `~/.aws/config`
AWS SSO	`aws configure sso` then `aws sso login --profile my-sso` and set `AWS_PROFILE=my-sso`
Static keys	Set `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` (and `AWS_SESSION_TOKEN` for temporary creds)
IAM role	Run on EC2/ECS/Lambda/EKS with an attached role; set only `AWS_REGION`

If access keys are omitted, the AWS SDK uses its default credential provider chain.

Creating an AWS profile

A profile is a named entry in ~/.aws/credentials and ~/.aws/config. Set AWS_PROFILE to that name in .env or MCP config.

Option A: Access keys (IAM user)

Requires AWS CLI.

aws configure --profile codepipeline-dev

You will be prompted for:

Prompt	Example
AWS Access Key ID	`AKIA...`
AWS Secret Access Key	(secret)
Default region name	`us-east-1`
Default output format	`json`

Then in .env:

AWS_REGION=us-east-1
AWS_PROFILE=codepipeline-dev

Option B: AWS SSO (IAM Identity Center)

aws configure sso --profile codepipeline-sso

GitHub で README 全文を見る

インストール

npx -y path/to/mcp-codepipeline-server/dist/index.js

MCP 初心者？mcpskill.org のガイドから始めましょう →

設定

{
   "mcpServers": {
    "codepipeline": {
      "command": "npx",
      "args": [
        "-y",
        "path/to/mcp-codepipeline-server/dist/index.js"
      ],
      "env": {
        "AWS_REGION": "us-east-1",
        "AWS_PROFILE": "your-aws-profile"
      }
    }
  }
}