Setup

Get a key, then add the server to your client. Two minutes, no payment, no approval step.

1. Get a key

Every field is optional and none is checked — they are recorded as claims and nothing is decided from them. Contact is worth giving anyway: it is the only way we could tell you about a breaking change or a price, and without it you find out when something stops working. Nothing is sent to it otherwise.

Mint a key on the front page, or below.

Or from a terminal:

curl -X POST https://skopia.datatreehaus.com/v1/keys \
  -H 'content-type: application/json' \
  -d '{"label":"my agent","contact":"you@example.com"}'

2. Add the server

Claude Code

claude mcp add --transport http skopia \
  https://skopia.datatreehaus.com/v1 \
  --header "Authorization: Bearer YOUR_KEY"

Codex CLI

Codex reads the token from an environment variable rather than from the config file, so export it first.

export SKOPIA_KEY=YOUR_KEY
codex mcp add skopia \
  --url https://skopia.datatreehaus.com/v1 \
  --bearer-token-env-var SKOPIA_KEY

Anything that reads .mcp.json

{
  "mcpServers": {
    "skopia": {
      "type": "http",
      "url": "https://skopia.datatreehaus.com/v1",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Straight HTTP

curl https://skopia.datatreehaus.com/v1 \
  -H "Authorization: Bearer YOUR_KEY" \
  -H 'content-type: application/json' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/list' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{"_meta":{
       "io.modelcontextprotocol/protocolVersion":"2026-07-28",
       "io.modelcontextprotocol/clientCapabilities":{}}}}'

3. Fewer tools, if you want them

Ten tools is standing context on every turn. A key can carry a profile (above), or you can point at a narrower endpoint directly — the endpoint wins if you set both.

/v1                 all ten
/v1/core            build and check
/v1/elevation       elevations and components
/v1/advisory        the reads that suggest and never decide
/v1/core+elevation  they compose

Managing your key

The key is its own credential — there are no accounts here. Check it, or revoke it, with the key itself:

curl https://skopia.datatreehaus.com/v1/keys/me \
  -H "Authorization: Bearer YOUR_KEY"

curl -X DELETE https://skopia.datatreehaus.com/v1/keys/me \
  -H "Authorization: Bearer YOUR_KEY"

Lost it? Revocation needs the key, so a lost key cannot be revoked — create a new one and abandon the old. It is rate-limited on its own bucket, so a stranger who found it could not spend your allowance for long.