mcp server seq
The Seq MCP Server enables interaction with Seq's API endpoints for logging and monitoring, providing tools for managing signals, events, and alerts with extensive filtering and configuration options.
The Seq MCP Server enables interaction with Seq's API endpoints for logging and monitoring, providing tools for managing signals, events, and alerts with extensive filtering and configuration options.
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.
get-signals
- Fetch signals with filtering optionsget-events
- Retrieve events with extensive filtering optionsget-alertstate
- Retrieve the current state of alertssignals
- List all shared signals with detailed informationThe 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 keyAdd 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"
}
}
}
}
Install dependencies:
npm install
Build the server:
npm run build
For development with auto-rebuild:
npm run dev
Run tests:
npm run test-script
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
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"
}
}
}
}
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
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 =======
[
{
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false,
"properties": {
"ownerId": {
"description": "Owner ID to filter signals by",
"type": "string"
},
"partial": {
"description": "Whether to include partial signal matches",
"type": "boolean"
},
"shared": {
"description": "Whether to include only shared signals (true) or private signals (false)",
"type": "boolean"
}
},
"type": "object"
},
"name": "get-signals"
},
{
"description": "Retrieve and analyze a list of event filtered by parameters. Use this tool when you need to: - Investigate events that are being logged in the SEQ server - Details of each event is a structured log and can provide usefull information - Events could be information, error, debug, or critical - Analyze error patterns and frequencies ",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false,
"properties": {
"count": {
"default": 100,
"description": "Number of events to return (max 100)",
"maximum": 100,
"minimum": 1,
"type": "number"
},
"filter": {
"description": "Filter expression for events",
"type": "string"
},
"fromDateUtc": {
"description": "Start date/time in UTC",
"type": "string"
},
"range": {
"description": "Time range (e.g., 1m, 15m, 1h, 1d, 7d)",
"enum": [
"1m",
"15m",
"30m",
"1h",
"2h",
"6h",
"12h",
"1d",
"7d",
"14d",
"30d"
],
"type": "string"
},
"signal": {
"description": "Comma-separated list of signal IDs",
"type": "string"
},
"toDateUtc": {
"description": "End date/time in UTC",
"type": "string"
}
},
"type": "object"
},
"name": "get-events"
},
{
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false,
"properties": {},
"type": "object"
},
"name": "get-alertstate"
}
]