openlaunch device MCP

Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.

Sign in to the openlaunch console. In Connections → API, create an agent API connection with read or read/action access and copy its ol_agent_ token, shown once. In Devices → Access, separately grant this exact connection the required functions. Send Authorization: Bearer <token>. For ol, run ol login or supply OPENLAUNCH_AGENT_TOKEN from a secret store. Device setup tokens and device credentials cannot authenticate an agent.

Connect an OAuth-capable MCP host to https://www.openlaunch.dev/mcp. Discover the resource and authorization server using RFC 9728 metadata. Use PKCE S256 and request openlaunch:read; also request openlaunch:act for device commands. The authorization server supports client ID metadata documents. Hosts requiring a registered client can use Connections → OAuth clients to register their exact callback URLs, then complete sign-in and consent. In Devices → Access, separately grant that exact OAuth connection its functions. OAuth consent never creates device grants.