Last9 MCP Server: Real-Time Production Logs & Traces

Overview

Last9 MCP Server implements the Model Context Protocol (MCP) to bring live production context — logs, metrics, and traces — directly into AI-enabled developer workflows. By connecting observability data to local MCP-capable tools and agents, you can surface real-time signals inside code assistants (Claude, Cursor, VS Code, etc.) to speed debugging and automate fixes with accurate, up-to-date context.

The project supports two modes: a hosted HTTP endpoint (recommended for speed and OAuth-based auth) and a self-hosted local binary running over STDIO (for environments that disallow direct HTTP or require local control). The server coordinates authentication with Last9, streams relevant telemetry, and exposes a set of MCP tools so agents can query and interact with production context from within the developer environment.

GitHub: https://github.com/last9/last9-mcp-server

Features

• Real-time production context: logs, metrics, and tracing data streamed into MCP clients
• Hosted HTTP mode with OAuth-based sign-in (no local token required)
• Self-hosted STDIO binary for offline or restricted environments
• Client-ready configurations for Claude, Cursor, VS Code, Windsurf and more
• Simple refresh-token auth for self-hosted use
• Portable installs: Homebrew, NPM, and pre-built release archives

Installation / Configuration

Quick note: choose hosted HTTP unless you need a local binary or your MCP client only supports STDIO.

Hosted (fastest, OAuth-based)

• Find your org slug in the Last9 URL: app.last9.io/<org_slug>/…
• Use this MCP URL in your client:

https://app.last9.io/api/v4/organizations/<org_slug>/mcp

Example: add to Claude Code

claude mcp add --transport http last9 https://app.last9.io/api/v4/organizations/<org_slug>/mcp

Cursor config (JSON)

{
  "mcpServers": {
    "last9": {
      "type": "http",
      "url": "https://app.last9.io/api/v4/organizations/<org_slug>/mcp"
    }
  }
}

VS Code (user settings)

{
  "mcp": {
    "servers": {
      "last9": {
        "type": "http",
        "url": "https://app.last9.io/api/v4/organizations/<org_slug>/mcp"
      }
    }
  }
}

Self-hosted (STDIO) — install options

Homebrew

brew install last9/tap/last9-mcp
# run:
last9-mcp

NPM

npm install -g @last9/mcp-server@latest
# or run inline:
npx -y @last9/mcp-server@latest

GitHub Releases

Self-hosted credentials

• Create a Refresh Token with Write permissions from Last9: app.last9.io/settings/api-access
• Provide the token via environment variable: LAST9_REFRESH_TOKEN

Example STDIO client config (generic JSON)

{
  "mcpServers": {
    "last9": {
      "command": "/opt/homebrew/bin/last9-mcp",
      "env": {
        "LAST9_REFRESH_TOKEN": "<last9_refresh_token>"
      }
    }
  }
}

For NPM-based invocation set command to npx and args to ["-y","@last9/mcp-server@latest"].

Available Tools / Resources

The MCP server exposes production observability tools that MCP-enabled clients and agents can use:

• Logs: tail, query, and paginate recent logs for a service or request
• Metrics: timeseries charts, thresholds, and recent anomalies
• Traces: fetch traces and spans for sampled requests, jump to spans for debugging
• Links: quick navigation to Last9 UI entries (incidents, traces, logs)
• Authentication: OAuth for hosted mode; refresh-token for self-hosted

See the project repository for code, examples, and release binaries: https://github.com/last9/last9-mcp-server

Use Cases

• Debugging a production error: open your code assistant (Claude/Cursor/VS Code Chat), connect the Last9 MCP server, and ask for recent errors for service X. The agent can show live logs and example traces related to the error, accelerating root cause identification.
• Auto-fix pull requests: an AI agent can correlate a failing test locally with recent production traces and propose a targeted code change, including exact span IDs and log snippets as evidence.
• Postmortem investigation: during incident review, stream metrics and tail logs directly into your editor or agent, annotate the timeline, and save links to traces and incidents for the runbook.
• Restricted environments: run the STDIO binary on a bastion or local workstation with a refresh token — no public HTTP endpoint required.

Getting Help & Contributing

• Read the repo README and issue tracker on GitHub: https://github.com/last9/last9-mcp-server
• Open an issue for bugs, feature requests, or ask for client-specific examples (Claude, Cursor, VS Code).
• Contributions via PRs are welcome — follow the repo contribution guidelines.

This guide should get you started connecting real-time Last9 observability into MCP-enabled developer tooling so agents and code assistants can act on accurate production context.