Start OAuth for a remote MCP server
start_mcp_server_oauthBegin the OAuth consent for a server bound as remote. Returns an authorizeUrl that a HUMAN must open in a browser signed in to the SHIP console as the same user this token acts for; the provider returns to the console, which stores the credential. The link is single-use and expires (expiresAt). An agent cannot complete the consent itself. Requires config:write.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>",
"serverName": "<serverName>"
},
"name": "start_mcp_server_oauth"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Requested scope; defaults to the server's own hint | |
| returnTo | No | Console path to land on after consent, e.g. /projects/<id> | |
| projectId | Yes | Project id, e.g. from list_projects | |
| serverName | Yes | Server name as the repository's MCP file declares it (see list_mcp_servers) |