Mcp Server Seq

By ahmad2x4 GitHub

mcp-server seq

Overview

What is Seq MCP Server?

Seq MCP Server is a server designed to interact with Seq's API endpoints, providing comprehensive access to logging and monitoring features through the Model Context Protocol.

How to use Seq MCP Server?

To use the Seq MCP Server, clone the repository, install dependencies, and configure it with your Seq server URL and API key. You can then run the server and integrate it with Claude Desktop.

Key features of Seq MCP Server?

Signals Management: Fetch and filter signals based on various criteria.
Event Management: Retrieve events with extensive filtering options and configurable counts.
Alert Management: Access the current state of alerts.
Type Safety: Utilizes TypeScript and Zod for type checking and validation.

Use cases of Seq MCP Server?

Managing and monitoring application logs.
Fetching and filtering specific events for analysis.
Integrating with other tools for enhanced logging capabilities.

FAQ from Seq MCP Server?

Is Seq MCP Server free to use?

Yes, it is open-source and available for anyone to use.

What programming language is used?

The server is built using JavaScript and TypeScript.

How do I report issues?

You can report issues on the GitHub repository's issue tracker.

Content

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: