Seq MCP Server

1

Add it to Claude Code

Run this in a terminal.

Run in terminal
claude mcp add -e "SEQ_URL=${SEQ_URL}" -e "SEQ_API_KEY=${SEQ_API_KEY}" seq-mcp -- docker build -t mcp/seq-otel .
Required:SEQ_URLSEQ_API_KEY
README.md

AI agent access to Datalust Seq instances for log analysis and monitoring

mcp-seq-otel

Standalone MCP server that gives AI agents controlled API access to a user-owned Datalust Seq instance.

What This Service Assumes

  • You already run/manage your own Seq instance.
  • This service only needs connection settings.

Required configuration:

  • SEQ_URL
  • SEQ_API_KEY

URL Support

SEQ_URL accepts either:

  • Host URL (recommended; service will append /api):
    • http://localhost:10150
    • https://seq.example.com
  • Full API base URL (also supported):
    • http://localhost:10150/api
    • https://seq.example.com/api

Available MCP Tools

  • seq_connection_test: validates Seq connectivity and API reachability, and reports the resolved root /health URL used for the check.
  • seq_starter_help: lists the compact starter alias tools.
  • seq_starter_overview: quick health, user, diagnostics, signals, and workspace summary.
  • seq_starter_events_search: common event search by filter/signal/time range.
  • seq_starter_event_by_id: fetch one event by id.
  • seq_starter_data_query: run a q query using GET or POST.
  • seq_starter_signals_list / seq_starter_signal_by_id: signal discovery helpers.
  • seq_starter_dashboards_list: list dashboards.
  • seq_starter_alerts_list: list alerts.
  • seq_starter_events_stream: bounded live-tail style stream call.
  • seq_api_catalog: returns the full official Seq route/verb/permission catalog.
  • seq_api_live_links: discovers live name -> route links from your Seq instance.
  • seq_api_request: generic verb/path invoker for any Seq API route.
  • seq_<verb>_<route>: auto-generated tool per official route+verb (from docs).

Scope note:

  • seq_starter_* tools are focused on common read workflows.
  • seq_api_request and seq_<verb>_<route> expose the broader HTTP API surface from the Seq endpoint catalog, including non-GET routes.

Seq API Key Permissions

Use least privilege based on the exact tools/workflows your MCP client will call.

Authoritative Datalust references:

Recommended permission profiles:

  • Read-focused starter usage (seq_starter_*, seq_connection_test, read-only queries): enable Read; disable Ingest, Write, Project, Organization, System.
  • Full route-surface usage (seq_api_request and seq_<verb>_<route>): required permissions depend on the specific route+verb; check seq_api_catalog or the official endpoint table before granting.

Permission guidance for this project:

Permission Needed now Why
Read Yes Required by starter query/retrieval workflows.
Ingest Usually No Needed only when calling ingestion routes such as ingest/* or api/events/raw when API-key-for-writing is required.
Write Maybe Needed for write routes (for example signals, dashboards, alerts, permalinks, SQL queries).
Project Maybe Needed for project-scoped administration and some settings/index routes.
Organization Maybe Needed for organization/user-management routes.
System Maybe Needed for system administration routes (for example apps, feeds, backups, updates).

Starter endpoint mapping in current implementation:

  • GET /health: public endpoint.
  • GET /api/events/resources: public endpoint.
  • GET /api/events: Read permission demand.
  • GET /api/events/{id}: Read permission demand.
  • GET /api/data: Read permission demand.

API Key Header

The server authenticates to Seq using the X-Seq-ApiKey header.

Resilience and Permission Handling

Tool failures are returned as structured MCP error responses (isError: true) instead of crashing the server process.

Current graceful handling includes:

  • 401 Unauthorized: returns guidance to verify SEQ_API_KEY and SEQ_URL.
  • 403 Forbidden: returns a permission-denied response with route-derived permission hints when available.
  • Network/timeout failures: returns connectivity diagnostics for AI clients.

Health check behavior:

  • seq_connection_test always probes the Seq host root at /health.
  • If SEQ_URL is configured as either http://host:port or http://host:port/api, the health check resolves to http://host:port/health.

Local Run (Node)

Node.js requirement: LTS (see .nvmrc).

npm install
npm run build

Windows PowerShell:

$env:SEQ_URL = "http://localhost:10150"
$env:SEQ_API_KEY = "your-key"
node dist/index.js

Docker Standalone Run

Docker Hub documentation assets in this repo:

Build image:

docker build -t mcp/seq-otel .

Run via Docker Compose (recommended for MCP stdio):

PowerShell:

./scripts/run-mcp-

Tools (6)

seq_connection_testValidates Seq connectivity and API reachability.
seq_starter_events_searchPerforms common event search by filter, signal, or time range.
seq_starter_data_queryExecutes a Seq data query using GET or POST.
seq_starter_dashboards_listLists available dashboards in the Seq instance.
seq_starter_alerts_listLists configured alerts in the Seq instance.
seq_api_requestGeneric verb/path invoker for any Seq API route.

Environment Variables

SEQ_URLrequiredThe URL of your Seq instance (e.g., http://localhost:10150)
SEQ_API_KEYrequiredThe API key for authenticating with your Seq instance

Configuration

claude_desktop_config.json
{"mcpServers": {"seq": {"command": "node", "args": ["/path/to/seq-mcp/dist/index.js"], "env": {"SEQ_URL": "http://localhost:10150", "SEQ_API_KEY": "your-key"}}}}

Try it

Check the health of my Seq instance and list the available dashboards.
Search for recent error events in the last hour using the 'Errors' signal.
Run a data query to count the number of events grouped by level.
List all active alerts currently configured in my Seq instance.
Fetch the details of the event with ID 'event-123'.

Frequently Asked Questions

What are the key features of Seq MCP?

Controlled read access to Datalust Seq instances. Support for both starter read workflows and full HTTP API surface. Structured error handling for 401 and 403 API responses. Auto-generated tools for official Seq API routes. Connectivity diagnostics and health checks.

What can I use Seq MCP for?

Automated log analysis for debugging production issues. Summarizing system health and alert status for incident response. Querying structured log data to identify performance bottlenecks. Discovering and retrieving dashboard data for reporting.

How do I install Seq MCP?

Install Seq MCP by running: npm install && npm run build

What MCP clients work with Seq MCP?

Seq MCP works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep Seq MCP docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Need the old visual installer? Open Conare IDE.
Open Conare