AWS CodePipeline MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pipelinesB | List all CodePipeline pipelines |
| get_pipeline_stateC | Get the state of a specific pipeline |
| list_pipeline_executionsC | List executions for a specific pipeline |
| approve_actionC | Approve or reject a manual approval action |
| retry_stageC | Retry a failed stage |
| trigger_pipelineC | Trigger a pipeline execution |
| get_pipeline_execution_logsC | Get logs for a pipeline execution |
| stop_pipeline_executionC | Stop a pipeline execution |
| get_pipeline_detailsC | Get the full definition of a specific pipeline |
| tag_pipeline_resourceC | Add or update tags for a pipeline resource |
| create_pipeline_webhookC | Create a webhook for a pipeline to enable automatic triggering |
| get_pipeline_metricsC | Get performance metrics for a pipeline |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cuongdev/mcp-codepipeline-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server