Authentication

Use a personal access token. It resolves to your Lemon Domains account and only ever touches your own data.

Bearer token (Claude Code, Cursor, CLI/CI)

Clients that let you set a request header authenticate with a personal access token. Create one on the MCP page, then send it on every request:

code

Authorization: Bearer lemd_xxxxxxxxxxxxxxxx

Shown once. Only a SHA-256 hash is stored; the raw value can't be recovered. Generate a new one if you lose it.
Prefix. Tokens start with lemd_; the dashboard shows the prefix so you can tell them apart.
Expiry. Optional: 30 days, 90 days, 1 year, or never.
Revocable. Revoke any time; the next request returns 401 immediately.

Treat a token like a password. It grants full read and write access to your portfolio. Prefer short-lived tokens for one-off tasks.

Connector clients (OAuth): coming soon

Connector clients like Claude.ai, Claude Desktop, and ChatGPT sign in with OAuth rather than a token. That flow is on the roadmap and not available yet. For now, use a header-capable client (Claude Code, Cursor, Windsurf, or any client that sends an Authorization header) with a personal access token.

How your data is scoped

Every tool only reads or writes data owned by your account.
Project roles are enforced: viewers can read but not write; some actions are owner-only.
Registrar API keys and secrets are never exposed via MCP.

← Quickstart Connect a client