Provides access to Seq signals, events, and alerts via MCP with configurable time ranges and API key authentication.
Configuration
View docs{
"mcpServers": {
"ahmad2x4-mcp-server-seq": {
"command": "npx",
"args": [
"-y",
"mcp-seq"
],
"env": {
"SEQ_API_KEY": "your-api-key",
"SEQ_BASE_URL": "your-seq-url"
}
}
}
}Seq MCP Server provides programmatic access to Seq’s API endpoints for interacting with your logging and monitoring system. It exposes signals, events, and alerts through a Model Context Protocol interface, allowing you to query and manage data from Seq in an automated, scriptable way.
You integrate the Seq MCP Server with an MCP client to access Seq features from your tooling. Start by choosing how you want to run the server: use a local runtime via a stdio-based command, or run through an npm/npx workflow. The server exposes signals, events, and alert state retrieval, letting you filter by owners, signals’ sharing status, and time ranges when fetching events.
Prerequisites: ensure you have Node.js installed on your machine. You will also need an active Seq instance and an API key.
If you want to run the server directly via a local runtime, you can use the following example configuration blocks to start the MCP server through your Claude Desktop setup. The first approach uses npx to run the MCP package, the second approach runs a prebuilt node script.
// Example 1: run via npx
// This starts the Seq MCP Server using the MCP package name
{
"mcpServers": {
"seq": {
"command": "npx",
"args": ["-y", "mcp-seq"],
"env": {
"SEQ_BASE_URL": "your-seq-url",
"SEQ_API_KEY": "your-api-key"
}
}
}
}
```
```
// Example 2: run via a local built script
// This starts the MCP server from a prebuilt sequence server file
{
"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"
}
}
}
}Environment variables you need are listed below. SEQ_BASE_URL is optional and defaults to http://localhost:8080 if not provided. SEQ_API_KEY is required to authenticate to Seq.
Time range options for fetching events are supported to tailor queries to specific intervals: 1m, 15m, 30m, 1h, 2h, 6h, 12h, 1d, 7d, 14d, and 30d.
Required environment variables for the server are: - SEQ_BASE_URL (optional): Your Seq server URL (defaults to http://localhost:8080) - SEQ_API_KEY (required): Your Seq API key
Development workflows include installing dependencies, building, and running in development mode. Typical commands are:
- npm install
- npm run build
- npm run dev
- npm run test-scriptThe get-events tool supports the following time range options: 1m, 15m, 30m, 1h, 2h, 6h, 12h, 1d, 7d, 14d, 30d.
This MCP server provides access to Signals, Events, Alerts, and Signals listings with detailed information such as IDs, titles, descriptions, owners, and sharing status. Use the available tools to fetch signals, filter events, and examine alert states.
Fetch signals with filtering options such as owner ID, shared/private status, and support for partial matches.
Retrieve events with extensive filtering options including signal IDs, custom filter expressions, configurable count (up to 100), and flexible time ranges.
Retrieve the current state of alerts.
List all shared signals with detailed information including Signal ID, title, description, sharing status, and owner information.