Seq

by ahmad2x4

3 Not rated yet MIT

GitHub

About

Integrates with Seq's API for retrieving signals, events, and alert states, enabling real-time insights into application logs and system performance metrics.

Details

Repository: ahmad2x4/mcp-server-seq
License: MIT

Explore

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below
Plugin Name Seq

Command (node, npx, python, etc.) npx
Arguments
- Argument 1 -y
- Argument 2 mcp-seq
Environment
- SEQ_API_KEY your-api-key
- SEQ_BASE_URL your-seq-url
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

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

JSON

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

JSON

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

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

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

JSON

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

JSON

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

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

From the repository

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

Run the following command to add the server:

claude mcp add --transport stdio \
  --env SEQ_BASE_URL=http://localhost:5341 \
  --env SEQ_API_KEY=your-api-key \
  seq -- npx -y mcp-seq

To share the configuration with your team, use the --scope project flag (saves to .mcp.json):

claude mcp add --transport stdio --scope project \
  --env SEQ_BASE_URL=http://localhost:5341 \
  --env SEQ_API_KEY=your-api-key \
  seq -- npx -y mcp-seq

> Windows users: Replace npx -y mcp-seq with cmd /c npx -y mcp-seq to avoid "Connection closed" errors.

Verify the server is connected by running /mcp inside Claude Code.

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"
      }
    }
  }
}

`get_signals`

Fetch signals with filtering options. Parameters: owner_id (optional string), shared (optional boolean), private (optional boolean), partial_match (optional boolean)

`get_events`

Retrieve events with extensive filtering options. Parameters: signal_ids (optional array), custom_filter (optional string), max_count (optional integer, default 50), time_range (optional string), date_range (optional string)

`get_alert_state`

Retrieve the current state of alerts.

`signals`

List all shared signals with detailed information. Returns: signal_id, title, description, sharing_status, owner_information

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 50) - Flexible time range options - Date range filtering

Alert Management

- get_alert_state - Retrieve the current state of alerts

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

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

Linux

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

Macos

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

Windows

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

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

Alert Management

- get_alert_state - 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

seq-ops Skill

This repo includes a Claude skill for Seq log analysis and incident investigation. Once the MCP server is connected, the skill guides Claude through structured investigations — health checks, incident triage, post-deployment monitoring — and produces consistent, actionable reports.

Install the skill:
```bash

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Explore

Setting up with Highlight

From the repository

get_signals

get_events

get_alert_state

signals

Signals Management

Event Management

Alert Management

Claude Desktop / Cursor

Linux

Macos

Windows

Features

Tools

Signals Management

Event Management

Alert Management

Resources

Signals Listing

Configuration

seq-ops Skill

More like this

Aws Kb Retrieval Server

Time

Github SSE

Npx Y convex@latest mcp start

`get_signals`

`get_events`

`get_alert_state`

`signals`