Getting started
Connect headless agents
Personal MCP access with a device code, without an SSH tunnel.
An agent on a Raspberry Pi or server can sign in using an OAuth device code. Choose your existing account for your context, or a separate account for independently owned context. A device code does not create a managed agent identity. Understand accounts and agents. The CLI needs neither a browser nor a callback listener. You approve access on another device.
Hermes
First configure https://meinkontext.de/mcp as a Streamable HTTP MCP server named context in Hermes. Then run:
hermes mcp login context --flow device- Open the displayed verification URL on your computer or phone.
- Sign in with the agent's own account if it should manage separate context. Check the displayed email before approval.
- Compare the device code and review the client, resource and permissions. Approve only a sign-in you started.
- Return to the CLI. It receives user-authorized OAuth access and saves credentials in its own credential store.
For a second account, open the link in a private browser window and sign in to that account. A different link does not automatically switch the signed-in account.
Codes expire after two hours. Start the CLI command again after expiry. Denied codes cannot subsequently be approved.
For “Too many requests” or HTTP 429, the client must honor the returned retry delay and continue with the same code while it remains valid. Concurrent sign-ins from the same network share a polling limit. Do not repeatedly restart sign-in; update a client that cannot wait and retry.
Access and limits
The agent receives its account's existing rights. It can manage its own context and consume permitted shared content. Plugin activation and permissions remain separate. A device code adds no organization or sharing privileges.
Org API keys are not a replacement: they provide a service principal and cannot publish context objects. Long-lived sessions require the client to request offline_access and support refresh tokens.
Other clients
The client must support RFC 8628. Discover endpoints in OAuth metadata. Register for urn:ietf:params:oauth:grant-type:device_code and, optionally, refresh_token. Use resource https://meinkontext.de/mcp. An existing authorization-code-only registration needs replacement with an appropriate registration.
Browser sign-in with PKCE remains available. Server support does not imply device-code support in every MCP client.