get_alert_state
Get the current state of all Seq alerts. Returns firing, ok, or suppressed status for each configured alert.
LABSCO SUMMARY
Reusing saved signals is the right entry point, because a team's signals already encode which noise to ignore.
A raw log query from an agent tends to return everything and then narrate it. Signals are filters somebody already tuned to separate the interesting from the constant, and pointing the query at one inherits that judgement for free. Reporting suppressed as a distinct alert state is the other detail worth having — an alert that is suppressed looks identical to one that is fine, and the difference is exactly what you want to know at three in the morning. Three tools, read-only, and it depends entirely on your Seq being well-organised.
What it is
A three-tool Seq client: list the saved signals, retrieve structured events, and read alert state.
What you get
- get_signals lists the saved named filters, and their ids are what get_events takes to narrow a query — so the team's existing definitions are reusable rather than reinvented.
- get_events retrieves structured log events for investigating errors and analysing behaviour.
- get_alert_state returns every alert as firing, ok or suppressed — suppressed being the state that explains why nobody was paged.
Requirements
SEQ_BASE_URL and SEQ_API_KEY — Seq is self-hosted, so the base URL is your own instance.
Setup effort
One command plus a key — npm install -g mcp-seq, then supply credentials
USE CASES
01
Investigating an error without drowning in logs
List the saved signals your team already tuned, then query events narrowed by the relevant one.
02
Finding out whether you should have been paged
Read every alert's state — firing, ok or suppressed — since a suppressed alert and a healthy one look the same from the outside.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_events
Retrieve structured log events from Seq. Use to investigate errors, analyze patterns, or monitor application health.
Tips:
- Call get_signals first to find signal IDs for targeted filtering
- Start with a broad time range, then narrow using filter expressions
- Filter expressions use Seq query syntax, e.g.: @Level = 'Error', StatusCode >= 500, RequestPath like '/api/%'
- Combine signal + filter for precise results
- Use render=true to get human-readable rendered messages instead of raw message templates
- Use the 'after' parameter with the last event ID to page through large result sets
get_signals
List saved Seq signals (named filters). Use signal IDs with get_events to narrow results to a specific service or category.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. The events tool is registered as get_events, though the documentation also spells it get-events. The README's signals entry is a resource listing, separate from the get_signals tool.
Requires
- npx on PATH
- SEQ_API_KEY in your environment
- SEQ_BASE_URL set to your Seq server's URL (optional; defaults to http://localhost:8080)
Where it runs
All 3 documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g mcp-seqMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport stdio --env SEQ_BASE_URL=http://localhost:5341 --env SEQ_API_KEY=<YOUR_SEQ_API_KEY> seq -- npx -y mcp-seqClaude Code — project scope
CLAUDE CODE — PROJECT SCOPE · TERMINAL
claude mcp add --transport stdio --scope project --env SEQ_BASE_URL=http://localhost:5341 --env SEQ_API_KEY=<YOUR_SEQ_API_KEY> seq -- npx -y mcp-seqClaude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"seq": {
"command": "npx",
"args": [
"-y",
"mcp-seq"
],
"env": {
"SEQ_BASE_URL": "<YOUR_SEQ_BASE_URL>",
"SEQ_API_KEY": "<YOUR_SEQ_API_KEY>"
}
}
}
}
