Overview
auralog exposes your logs and analyses through two read-only surfaces. MCP is the main path for AI agents; REST is available when you need direct HTTP access.
- MCP server at
https://mcp.auralog.ai/mcp— Model Context Protocol over Streamable HTTP. Lets Codex, Claude, Cursor, and other MCP clients query auralog directly during a conversation. - REST API at
https://api.auralog.ai/v1/*— standard JSON. Fully described by an OpenAPI 3.1 document.
Both surfaces are backed by the same data and use the same authentication. Pick the one that fits your client.
When to use which
Section titled “When to use which”| You want to… | Use |
|---|---|
| Let Codex, Claude, Cursor, or another agent investigate logs during a conversation | MCP |
| Build a custom dashboard, alerting integration, or pipeline | REST |
| Pipe analyses into Slack via a script | REST |
One-off curl from your terminal | REST |
Authentication
Section titled “Authentication”Both surfaces authenticate with read keys. They are separate from ingest keys (which the SDK uses to send logs):
- Ingest keys —
aura_*— write-only, used by SDKs. - Read keys —
aura_read_*— read-only, scoped to a single project.
New projects show one plaintext read key in the startup modal. You can also create additional read keys from the project’s Settings → API & MCP keys panel. Plaintext is shown once on creation; copy it then.
A read key only ever sees its own project — list_projects returns just that one row. Read keys cannot write logs or modify anything; the scope is fixed at creation and cannot be elevated.
What you can read
Section titled “What you can read”| Resource | List | Get one | Search |
|---|---|---|---|
| Projects | yes (returns the one scoped project) | yes | — |
| Logs | yes (filter by level, time range) | yes (with full context) | yes (full-text) |
| Analyses | yes (filter by severity, type; archived hidden by default) | yes | — |
Limits
Section titled “Limits”- Rate limit: 60 requests per minute per read key.
- Page size: up to 200 items per request; pagination via cursor.
- Project scope: one read key resolves to one project. Calling tools with a different
project_idreturnsproject_id does not match the read key's scope.
Next steps
Section titled “Next steps”- Setup — wire up Codex, Claude, Cursor, or another MCP client.
- MCP Tools Reference — full list of tools with arguments and examples.
- REST API — endpoint reference for direct HTTP use.