Bind an MCP server
bind_mcp_serverDestructiveIdempotent
Create or update the binding for a server the repository declares. roles is the full set of pipeline roles that may use it (reviewer and qa only ever receive read-only tools, and cannot use a server that runs inside the sandbox). transport: 'remote' (the gateway proxies to the server's URL), 'isolate' (the gateway runs the server's npm package in isolation, for a command that needs a secret) or 'local' (the command runs inside the sandbox, no credential). Omit transport and remoteUrl on an update to keep the server the binding is pinned to, with its credential (a roles, tools or credential edit); set them only to bind or re-point the server. Requires the config:write capability.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| roles | Yes | Every role that may use the server ([] disables it) | |
| projectId | Yes | Project id, e.g. from list_projects | |
| remoteUrl | No | A fixed https URL: a hosted endpoint for a command server, or an override for a URL server | |
| transport | No | ||
| credential | No | Write-only credential the gateway attaches; agents never receive it. Omit to keep the stored one. OAuth credentials are not set here: bind as remote with kind 'none', then start_mcp_server_oauth. | |
| serverName | Yes | Server name as the repository's MCP file declares it (see list_mcp_servers) | |
| approvedTools | No | The approved subset of the tool snapshot (refresh_mcp_server_tools first). Omit to keep it. |