CodePipelineProcessMcpServer
An MCP server that runs from a repository’s checkout over standard input and output, so a run’s agents can call the repository’s own tools. Coding tools that support such servers start it in the checkout folder.
Kind: an object, used in requests and responses. In a request it is called CodePipelineProcessMcpServerInput.
In a request
Section titled “In a request”| Field | Type | Required | Description |
|---|---|---|---|
command | string | The program that starts the server, for example node, python or npx. | |
args | string[] | The arguments to pass to command, for example ["dist/server.js"]. May be empty. |
{ "command": "...", "args": [ "..." ]}In a response
Section titled “In a response”Every field is present in a response; empty ones are null.
| Field | Type | Description |
|---|---|---|
command | string | The program that starts the server, for example node, python or npx. |
args | string[] | The arguments to pass to command, for example ["dist/server.js"]. May be empty. |
{ "command": "...", "args": [ "..." ]}Where it’s used
Section titled “Where it’s used”- Inside
CodePipelineGitHttpRepo - Inside
CodePipelineGitSshRepo