Skip to main content
Glama

Start OAuth for a remote MCP server

start_mcp_server_oauth

Begin 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoRequested scope; defaults to the server's own hint
returnToNoConsole path to land on after consent, e.g. /projects/<id>
projectIdYesProject id, e.g. from list_projects
serverNameYesServer name as the repository's MCP file declares it (see list_mcp_servers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.