Repository files navigation

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.

Author: Cuong T Nguyen

• 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, CloudWatch, and IAM (for tagging)
• Windsurf IDE with Cascade AI assistant

1. Clone this repository:

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

2. Install dependencies:

npm install

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

cp .env.example .env

4. Update the.env file with your AWS credentials and configuration:

AWS_REGION=us-east-1AWS_ACCESS_KEY_ID=your_access_key_idAWS_SECRET_ACCESS_KEY=your_secret_access_keyPORT=3000

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

npm run build

npm start

For development with auto-restart:

npm run dev

This MCP server is designed to work with Windsurf, allowing Cascade to interact with AWS CodePipeline through natural language requests.

1. Make sure the server is running:

npm start

2. Add the server configuration to your Windsurf MCP config file at~/.codeium/windsurf/mcp_config.json:

{"mcpServers": {"codepipeline": {"command":"npx","args": ["-y","path/to/mcp-codepipeline-server/dist/index.js"      ],"env": {"AWS_REGION":"us-east-1","AWS_ACCESS_KEY_ID":"your_access_key_id","AWS_SECRET_ACCESS_KEY":"your_secret_access_key"      }    }  }}

3. Create the directory if it doesn't exist:

mkdir -p~/.codeium/windsurftouch~/.codeium/windsurf/mcp_config.json

4. Restart Windsurf to load the new MCP server configuration

Once configured, you can interact with AWS CodePipeline using natural language in Windsurf. For example:

• "List all my CodePipeline pipelines"
• "Show me the current state of my 'production-deploy' pipeline"
• "Trigger the 'test-build' pipeline"
• "Get metrics for my 'data-processing' pipeline"
• "Create a webhook for my 'frontend-deploy' pipeline"

Cascade will translate these requests into the appropriate MCP tool calls.

1. Connection refused error:

   • Ensure the server is running on the specified port
   • Check if the port is blocked by a firewall

2. AWS credential errors:

   • Verify your AWS credentials in the.env file
   • Ensure your IAM user has the necessary permissions

3. Windsurf not detecting the MCP server:

   • Check themcp_config.json file format
   • Ensure the server URL is correct
   • Restart Windsurf after making changes

The server logs information to the console. Check these logs for troubleshooting:

# Run with more verbose loggingDEBUG=* npm start

{"pipelineName":"my-pipeline","webhookName":"github-webhook","targetAction":"Source","authentication":"GITHUB_HMAC","authenticationConfiguration": {"SecretToken":"my-secret-token"  },"filters": [    {"jsonPath":"$.ref","matchEquals":"refs/heads/main"    }  ]}

{"pipelineName":"my-pipeline","period":86400,"startTime":"2025-03-10T00:00:00Z","endTime":"2025-03-17T23:59:59Z"}

ISC