What is Mcp Server Seq

mcp-server-seq is a server designed to interface with Seq’s API endpoints, enabling interaction with logging and monitoring systems through the Model Context Protocol.

Use cases

Use cases for mcp-server-seq include monitoring application logs, managing alerts, and analyzing event data in real-time for better decision-making and system performance.

How to use

To use mcp-server-seq, configure your Claude Desktop by adding the server settings in the ‘claude_desktop_config.json’ file, including your Seq server URL and API key. Install dependencies and build the server using npm commands.

Key features

Key features include signal management with filtering options, event management with extensive filtering capabilities, and alert state retrieval. It supports various time range options for event queries and provides detailed signal listings.

Where to use

undefined

Seq MCP Server

MCP Server for Seq’s API endpoints for interacting with your logging and monitoring system. This server provides comprehensive access to Seq’s API features through the Model Context Protocol.

Features

Tools

Signals Management

• get-signals - Fetch signals with filtering options
  • Filter by owner ID
  • Filter shared/private signals
  • Support for partial matches

Event Management

• get-events - Retrieve events with extensive filtering options
  • Filter by signal IDs
  • Custom filter expressions
  • Configurable event count (max 100)
  • Flexible time range options
  • Date range filtering

Alert Management

• get-alertstate - Retrieve the current state of alerts

Resources

Signals Listing

• signals - List all shared signals with detailed information
  • Signal ID
  • Title
  • Description
  • Sharing status
  • Owner information

Configuration

The server requires the following environment variables:

• SEQ_BASE_URL (optional): Your Seq server URL (defaults to ‘http://localhost:8080’)
• SEQ_API_KEY (required): Your Seq API key

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "seq": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-seq"
      ],
      "env": {
        "SEQ_BASE_URL": "your-seq-url",
        "SEQ_API_KEY": "your-api-key"
      }
    }
  }
}

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run dev

Run tests:

npm run test-script

Time Range Options

The get-events tool supports the following time range options:

• 1m - Last minute
• 15m - Last 15 minutes
• 30m - Last 30 minutes
• 1h - Last hour
• 2h - Last 2 hours
• 6h - Last 6 hours
• 12h - Last 12 hours
• 1d - Last day
• 7d - Last 7 days
• 14d - Last 14 days
• 30d - Last 30 days

Installation

This tool is still in development and we havn’t pushed to the npm repository. You need to clone this repository on your local then build npm run build

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "seq": {
      "command": "node",
      "args": [
        "/Users/ahmadreza/source/ahmad2x4/mcp-server-seq/build/seq-server.js"
      ],
      "env": {
        "SEQ_BASE_URL": "your-seq-url",
        "SEQ_API_KEY": "your-api-key"
      }
    }
  }
}

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. The server implements proper error handling and logging for all operations. You can run the test script to verify functionality:

npm run test-script

Type Safety

The server implements comprehensive type safety using:

• TypeScript for static type checking
• Zod schema validation for runtime type checking
• Proper error handling and response formatting
  =======