One endpoint. It handles the OAuth itself — there is no key to paste.
https://central.konsole.one/mcp
Add the URL above as a remote MCP server. The client will find it needs authorisation, register itself, and send you here to sign in. Approve it once, and everything you have been granted is reachable.
From Claude Codeclaude mcp add --transport http central https://central.konsole.one/mcp
For something that is not a person
A cron job or a CI step cannot sit through a consent screen. Mint it
a key instead — token.issue, or the button on your Overview — and send it as
a bearer token.
curl -s https://central.konsole.one/mcp \ -H 'authorization: Bearer hauth_…' \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'What a downstream tool needs
Nothing. This server mints keys through each tool's own key-minting
operation and calls it over its own MCP endpoint. If a tool would rather verify tokens itself, the key set is at
/auth/jwks and there is an introspection endpoint at /auth/oauth2/introspect — but neither
is required.
The tool list is always the same four. When discover_tools
comes back empty it means one of two things: nothing is connected here yet, or nothing has been granted to you.
execute with grant.explain says which, by name.