Skip to content
Lumindocs
UseBuild
Open Lumin

Reference

Authentication

Lumin supports three auth modes against two endpoints. Pick the one that fits your integration.

Endpoints

EndpointAcceptsUse for
https://mcp.lumin.guru/mcpAnonymous, API keyService-to-service, scripting, public demos
https://mcp.lumin.guru/mcp/authOAuth 2.1 JWTPer-user integrations, claude.ai, public clients

API key

Generate a key at app.lumin.guru/developer. Keys are prefixed mcp_ followed by a random suffix.

Authorization: Bearer mcp_abc123...

Keys can be tier-scoped (free, starter, pro, enterprise). The tier controls daily limits and which higher-tier tools are allowed. Keys are revocable at any time and do not require client-side rotation logic. Pull a new one and replace.

OAuth 2.1

Lumin proxies Supabase Auth to expose standard OAuth 2.1 endpoints:

GET  /.well-known/oauth-protected-resource
GET  /.well-known/oauth-authorization-server
GET  /authorize
POST /token
POST /register

For claude.ai connectors, the discovery flow is automatic. Paste the auth endpoint URL and Claude will run the consent flow. For custom clients, follow the standard authorization-code-with-PKCE flow against the discovery document.

Anonymous

No header required on /mcp. Limited to 50 calls per day per IP. Useful for quickstart, demos, and read-only integrations where attribution is not needed.

PreviousAll toolsNextError codes