MicroApps

Appearance

API keys & automation ​

An API key is a reusable credential for scripts, servers, and assistants - anything that talks to MicroApps without a human logging in. Unlike a login token, a key does not expire; you revoke it when you are done with it.

Create a key ​

  1. Go to Account Settings -> API keys and create one. Give it a name you will recognise later ("deploy-ci", "status-dashboard").
  2. Scope it. Grant only the permissions it needs - pods:read for a dashboard, pod and snapshot permissions for a deploy script, and so on. A key with no permissions set gets full access capped to your own, which is rarely what you want, so be specific.
  3. Optionally IP-bind it. Add one or more IP addresses or CIDR ranges and the key only works from there.
  4. Copy the key. It starts with mck_ and is shown once - store it somewhere safe, such as a secret manager or your CI's encrypted variables. If you lose it, revoke it and make a new one.

Keys cannot manage your team, roles, or account settings. Those need a signed-in person, on purpose.

Call the REST API ​

Send the key as a bearer token - the same header the console uses:

bash
export MCK_KEY="mck_..."

curl https://cloud-api.microapps.io/api/pods \
  -H "Authorization: Bearer $MCK_KEY"

That lists your pods. Everything in the API reference works the same way; the key just needs the matching permission, or you get a 403.

bash
curl https://cloud-api.microapps.io/api/billing/stats \
  -H "Authorization: Bearer $MCK_KEY"

Connect an MCP client ​

The same key connects an assistant like Claude through MCP. In your client's MCP settings, add an HTTP server pointing at:

https://cloud-api.microapps.io/mcp

and set the authorization header to Bearer <your mck_ key>. The assistant then sees the tools your key is allowed to use - give it a read-only key and it can report on your account but not change anything.

Least privilege

Make one key per job and scope each one tightly. If a key leaks, you revoke that one key and nothing else is affected.

Revoke a key ​

Delete it from the API keys page. It stops working immediately, everywhere.

See also ​

Built for the long tail.

© 2026 MicroApps