Reference
API keys
Agents and the CLI sign in with your browser, so most people never need a key. Keys are for scripts, CI and self-hosted servers without Google sign-in. Each key belongs to one workspace and can use everything in it.
Docs menu
When to use a key
| Use | Sign in with |
|---|---|
| Claude Code, Codex, Cursor… | The browser (OAuth). Setup. |
| The CLI on your machine | The browser: pnpm meerko login. |
| Scripts, CI, servers | An API key. |
| Self-hosted, no Google sign-in | An API key, for agents and the CLI too. |
Creating a key
In the dashboard, open Settings → API keys, name the key and create it. Keys start with mk_ and are shown once, so copy it straight away. Creating and revoking keys needs you signed in to the dashboard with Google. Self-hosted installs also get a key from pnpm db:seed.
Using a key
| Where | How |
|---|---|
| HTTP | Send it as a bearer token: Authorization: Bearer mk_…. |
| MCP | The same header on https://api.meerko.ai/mcp. Example. |
| CLI | pnpm meerko login --key mk_… --url https://api.meerko.ai, or set MEERKO_API_KEY. |
$ curl -H "Authorization: Bearer mk_…" https://api.meerko.ai/v1/tables
Revoking
Delete a key from the same list in Settings. Anything using it stops working straight away. The list shows when each key was last used, which helps spot the ones nobody needs. Apps that signed in with the browser are under Connected apps on the same page.
How keys are stored
Meerko stores only a hash of each key and its first characters, to tell keys apart. Nobody, including us, can show you a key again, which is why you copy it on creation. Lost one? Revoke it and create another.