MCP Setup

The auralog MCP server lets AI agents query your logs and analyses directly during a conversation — no copy-paste, no context switching. Use it with Codex, Claude, Cursor, or any MCP client that supports Streamable HTTP.

Prerequisites

You need a read key for your project.

If you just created the project, copy the MCP/API read key from the startup modal.

If you need another, open your project in the auralog dashboard, go to Settings → API & MCP keys, click Create under Read keys, and copy the plaintext key (aura_read_…). It is only shown once.

The MCP endpoint is https://mcp.auralog.ai/mcp (Streamable HTTP transport).

Claude Code

The fastest path. From inside the project where you want to use auralog:

claude mcp add --transport http auralog https://mcp.auralog.ai/mcp \
  --header "Authorization: Bearer aura_read_YOUR_KEY"

Verify the connection:

claude mcp list | grep auralog
# auralog: https://mcp.auralog.ai/mcp (HTTP) - ✓ Connected

Restart Claude Code. The auralog tools (list_projects, list_logs, list_analyses, etc.) will be available in the next session.

Scope

The default --scope local adds the server to the current project only. Use --scope user to make it available everywhere.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "auralog": {
      "transport": {
        "type": "http",
        "url": "https://mcp.auralog.ai/mcp",
        "headers": {
          "Authorization": "Bearer aura_read_YOUR_KEY"
        }
      }
    }
  }
}

Restart Claude Desktop. The auralog tools will appear in the tools menu.

Older Claude Desktop versions (stdio bridge)

If your Claude Desktop build doesn’t support HTTP transport yet, use mcp-remote as a stdio bridge:

{
  "mcpServers": {
    "auralog": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.auralog.ai/mcp",
        "--header",
        "Authorization: Bearer aura_read_YOUR_KEY"
      ]
    }
  }
}

Codex, Cursor, and other MCP clients

The server speaks standard MCP over Streamable HTTP. Any client that supports HTTP transport with bearer auth will work. Smoke-test with curl:

curl -X POST https://mcp.auralog.ai/mcp \
  -H "Authorization: Bearer aura_read_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "capabilities": {},
      "clientInfo": { "name": "test", "version": "0" }
    }
  }'

A 200 with a result.serverInfo.name = "auralog" confirms auth and transport.

Try it

Once connected, ask your agent something like:

• “What’s broken in production right now?”
• “Pull the last 20 error logs and look for patterns.”
• “Show me the most recent high-severity analysis.”

Your client will pick the right tool, scope to your project, and summarize. See the Tools Reference for what’s available.

Rotating or revoking a key

Revoking a read key is immediate — clients using the old key will start getting 401s on the next request. To rotate:

1. Create a new read key in the dashboard.
2. Update your client config with the new key.
3. Revoke the old key.

There is no grace window. Plan rotations during quiet hours.