The AWS CodePipeline MCP server provides a standardized interface that integrates with AWS CodePipeline, allowing you to manage your pipelines through Windsurf and Cascade. It enables you to perform various pipeline operations using natural language requests in the Windsurf IDE.
git clone https://github.com/cuongdev/mcp-codepipeline-server.git
cd mcp-codepipeline-server
npm install
cp .env.example .env
.env
file with your AWS credentials:AWS_REGION=us-east-1
AWS_ACCESS_KEY_ID=your_access_key_id
AWS_SECRET_ACCESS_KEY=your_secret_access_key
PORT=3000
Build the project:
npm run build
Start the server:
npm start
For development with auto-restart:
npm run dev
Ensure the server is running.
Create or edit your Windsurf MCP config file:
mkdir -p ~/.codeium/windsurf
touch ~/.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"
}
}
}
}
Once configured, you can use natural language in Windsurf to interact with AWS CodePipeline. Examples:
Tool Name | Description | Parameters |
---|---|---|
list_pipelines |
List all pipelines | None |
get_pipeline_state |
Get pipeline state | pipelineName : Pipeline name |
list_pipeline_executions |
List pipeline executions | pipelineName : Pipeline name |
trigger_pipeline |
Trigger pipeline execution | pipelineName : Pipeline name |
stop_pipeline_execution |
Stop pipeline execution | pipelineName , executionId , reason (optional) |
Tool Name | Description | Parameters |
---|---|---|
get_pipeline_details |
Get full pipeline definition | pipelineName : Pipeline name |
get_pipeline_execution_logs |
Get execution logs | pipelineName , executionId |
get_pipeline_metrics |
Get performance metrics | pipelineName , period (optional), startTime (optional), endTime (optional) |
Tool Name | Description | Parameters |
---|---|---|
approve_action |
Approve/reject manual actions | pipelineName , stageName , actionName , token , approved , comments (optional) |
retry_stage |
Retry failed stage | pipelineName , stageName , pipelineExecutionId |
tag_pipeline_resource |
Add/update resource tags | pipelineName , tags (key-value pairs) |
create_pipeline_webhook |
Create pipeline webhook | pipelineName , webhookName , targetAction , authentication , etc. |
Connection refused error:
AWS credential errors:
.env
fileWindsurf not detecting the MCP server:
mcp_config.json
file formatFor more verbose logging:
DEBUG=* npm start
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.