Auralogs

ai.auralogsPublished by auralogs.aiOfficial publisherv0.1.0Updated Oct 24, 2026

Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Read-only access to Auralogs production logs, letting an assistant search logs, inspect errors, and review AI analyses.

What you can do
A hosted, read-only MCP server for the Auralogs logging platform. Tools include list_projects, get_project, list_logs, search_logs, get_log, list_analyses, and get_analysis, covering log listing and full-text search plus AI-generated diagnoses with suggested fixes and PR links. No write tools exist, so agents can look but not change anything.
When to use it
Useful when you want an assistant to answer questions like what is broken in production right now, pull recent error logs and look for patterns, or surface the latest high-severity analysis, instead of copy-pasting stack traces into a chat.
Requirements
A remote Streamable HTTP endpoint at Requires an Auralogs account and a project-scoped read key sent in the Authorization header as a bearer token. Rate limit is 60 requests per minute per key.
Before you install
The Authorization header carries a project-scoped read key; treat it as a secret and revoke it from the dashboard if exposed. Access is read-only and scoped to one project, and log content is sent to the assistant and its model provider.

Installation

In SourceWeft

  1. Open Auralogs in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.auralogs%2Fauralogs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "auralogs": {
      "type": "http",
      "url": "https://mcp.auralogs.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

[Auralogs]

Auralogs MCP Server

Hosted, read-only MCP server for Auralogs, the logging platform built for AI-assisted teams. Connect Claude Code, Claude Desktop, Cursor, Codex, Cline, or any Streamable HTTP MCP client to your production logs, then ask your agent "what's broken in production right now?" instead of copy-pasting stack traces.

[Add to Cursor] [Docs]

  • Endpoint: https://mcp.auralogs.ai/mcp (Streamable HTTP)
  • Auth: Authorization: Bearer aura_read_... (project-scoped read key)
  • Read-only by design: no write tools exist. Agents can look, not touch.
  • Rate limit: 60 requests/minute per key

Tools

ToolDescription
list_projectsList projects accessible to the current read key
get_projectGet a project by id
list_logsList logs, filtered by level and time range
search_logsFull-text search across log messages
get_logGet a single log with full context (stack, metadata)
list_analysesList AI analyses, filtered by severity and type
get_analysisGet one analysis (diagnosis, suggested fix, PR link)

Get a key

  1. Sign up free at auralogs.ai (10,000 logs/month, no credit card).
  2. Create a project and copy the MCP/API read key from the startup modal, or create one later under Settings → API & MCP keys → Read keys.

Keys look like aura_read_..., are scoped to one project, and can be revoked instantly from the dashboard.

Connect

Claude Code

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

Claude Desktop

Add to claude_desktop_config.json:

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

Cursor

Click the Add to Cursor badge above, or add to .cursor/mcp.json:

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

Cline

Add via the Remote Servers tab, or in cline_mcp_settings.json:

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

Codex

See auralogs-codex for the Codex plugin, or use any standard remote MCP configuration.

Anything else

The server speaks standard MCP over Streamable HTTP with bearer auth. Smoke-test with curl:

bash
curl -X POST https://mcp.auralogs.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 result.serverInfo.name = "auralogs" confirms auth and transport.

Try it

Once connected, ask your agent:

  • "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."

Security

  • Read keys are read-only and scoped to a single project. The MCP surface exposes no write operations.
  • Revocation is immediate: revoked keys get 401 on the next request.
  • Keys are stored hashed (SHA-256); the plaintext is shown once at creation.

Full documentation: docs.auralogs.ai/read-api

About this repo

This repo holds the public metadata for the hosted Auralogs MCP server: the MCP Registry server.json, install instructions, and listing assets. The server itself is a hosted service; there is nothing to install from here.

Source: README.md at commit f48dc37

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts