Skip to content

Tokens

Machine credentials for the CLI, the API, and your own AI agent over the MCP server. A token is issued only here, by a person — pick what it may do, review the operations, and mint. The full token is shown once.

Issuing is restricted

Sign in to a tenant to issue and manage machine tokens — the example dataset has none.

Connect an agent

Every setup reads the token from LOGLUNE_OPERATOR_TOKEN (VS Code asks for it), so no config file or shell history holds it. The server tells the agent how to use each operation; billed and state-changing ones need its confirmation. Agent docs

CLI

npm install --global @loglune/cli
read -rs LOGLUNE_OPERATOR_TOKEN && export LOGLUNE_OPERATOR_TOKEN
loglune inspect

Claude Code

claude mcp add --transport http --scope project loglune https://loglune.com/api/mcp --header 'Authorization: Bearer ${LOGLUNE_OPERATOR_TOKEN}'

.mcp.json

{
  "mcpServers": {
    "loglune": {
      "type": "http",
      "url": "https://loglune.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${LOGLUNE_OPERATOR_TOKEN}"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "loglune": {
      "url": "https://loglune.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:LOGLUNE_OPERATOR_TOKEN}"
      }
    }
  }
}

VS Code (.vscode/mcp.json)

{
  "inputs": [
    {
      "type": "promptString",
      "id": "loglune-token",
      "description": "Loglune operator token",
      "password": true
    }
  ],
  "servers": {
    "loglune": {
      "type": "http",
      "url": "https://loglune.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:loglune-token}"
      }
    }
  }
}

Tokens

Every machine credential on this tenant, with the capability it was granted and who issued it.

Sign in to a tenant to issue and manage machine tokens.