Zuey.me API

Manage personal keys openapi.json

“Test Request” only calls this site (same origin). If you are signed in, your member session cookie is used. Or paste a personal key (zk_…) below: it lives in this tab's memory only (never in the URL, storage or analytics) and is sent as Authorization: Bearer with cookies omitted. Every POST/PUT/PATCH/DELETE asks for confirmation before it is sent.

REST, CLI and MCP examples

REST

curl -H "Authorization: Bearer $ZUEY_API_KEY" https://zuey.me/api/v1/me
curl -H "Authorization: Bearer $ZUEY_API_KEY" https://zuey.me/api/v1/articles

CLI

zuey login                       # paste a zk_ key (input hidden, saved with 0600 permissions)
zuey whoami
zuey articles list
zuey subscribe <plan> --months 3
zuey mcp config

MCP (OAuth, recommended)

{
  "mcpServers": {
    "zuey": {
      "type": "http",
      "url": "https://zuey.me/mcp"
    }
  }
}

MCP (personal key header)

{
  "mcpServers": {
    "zuey": {
      "type": "http",
      "url": "https://zuey.me/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_ZK_KEY>"
      }
    }
  }
}

MCP clients discover OAuth from /.well-known/oauth-protected-resource/mcp. Connected apps can be disconnected at /account.