Auralogs

Name: Auralogs
Author: auralogs-ai

@auralogs-ai

About Auralogs

Hosted, read-only MCP server for Auralogs production logs. Agents search logs, inspect errors with full stack and metadata, and review AI analyses (diagnosis, suggested fix, PR link) over Streamable HTTP with a project-scoped read key. Free tier: 10,000 logs/month.

#logging #observability #debugging #production #devops #error-tracking

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "auralogs": {
      "url": "https://mcp.auralogs.ai/mcp",
      "headers": {
        "Authorization": "Bearer aura_read_YOUR_KEY"
      }
    }
  }
}

Tools

List projects accessible to the current read key (one project for v1).

Get a project by id. Must match the read key's scoped project.

List logs for the scoped project, optionally filtered by level/since/until.

Full-text search log messages for the scoped project.

Get a single log row by id, with full context (stack, metadata).

List active analyses for the scoped project. Archived analyses (triaged from the dashboard) are excluded by default; pass include_archived=true to see them. Optional filters: severity (low/medium/high/critical), type (reactive/scheduled).

Get a single analysis by id (diagnosis, suggested fix, PR link if any).

Overview

What is Auralogs?

Auralogs is a hosted, read-only MCP server for the Auralogs logging platform, designed for AI-assisted teams. It connects Claude, Cursor, Cline, Codex, or any Streamable HTTP MCP client to production logs so agents can query log data and analyses directly.

How to use Auralogs?

Obtain a project-scoped read key (aura_read_...) from the Auralogs dashboard. Then configure your MCP client with endpoint https://mcp.auralogs.ai/mcp and the header Authorization: Bearer aura_read_YOUR_KEY. For Claude Desktop, add the configuration to claude_desktop_config.json; for Claude Code, use claude mcp add --transport http auralogs https://mcp.auralogs.ai/mcp --header "Authorization: Bearer aura_read_YOUR_KEY".

Key features of Auralogs

Read-only by design (no write tools exist)
Uses standard MCP over Streamable HTTP
Rate limited to 60 requests per minute per key
Supports Claude Desktop, Claude Code, Cursor, Cline, and Codex
Keys are project-scoped and instantly revocable
Full-text search across log messages and AI analyses

Use cases of Auralogs

Ask an AI agent “What’s broken in production right now?” without copy‑pasting stack traces
Query recent error logs and search for patterns
Review the latest high‑severity AI analysis with diagnosis, suggested fix, and PR link
Integrate production log inspection directly into coding workflows inside MCP‑compatible IDEs

FAQ from Auralogs

What is the server endpoint?

The endpoint is https://mcp.auralogs.ai/mcp using Streamable HTTP transport.

How do I authenticate?

Use bearer authentication with a project‑scoped read key (aura_read_...) passed in the Authorization header.

Is the MCP server read-only?

Yes. The server exposes only read tools (e.g., list_logs, search_logs, get_analysis). No write operations are available.

What are the rate limits?

Rate limit is 60 requests per minute per key.

How do I get a read key?

Sign up for free at auralogs.ai, create a project, and copy the MCP/API read key from the startup modal or from Settings → API & MCP keys → Read keys.