Seq MCP Server logo

Seq MCP Server

by ahmad2x4

MCP Server for Seq's API endpoints, providing comprehensive access to Seq's logging and monitoring system through the Model Context Protocol. It allows interaction with Seq's API features.

View on GitHub

Last updated: N/A

What is Seq MCP Server?

This is an MCP (Model Context Protocol) server that acts as an interface to Seq's API. It enables users to interact with their Seq logging and monitoring system through a standardized protocol.

How to use Seq MCP Server?

To use, configure the server with your Seq server URL and API key via environment variables. Then, integrate it with a compatible MCP client, such as Claude Desktop, by adding the server configuration to the client's configuration file. The server provides tools for managing signals, events, and alerts within Seq.

Key features of Seq MCP Server

  • Signals Management (get-signals)

  • Event Management (get-events) with extensive filtering

  • Alert Management (get-alertstate)

  • Signals Listing (signals)

  • Comprehensive type safety using TypeScript and Zod

  • Configurable time range options for event retrieval

Use cases of Seq MCP Server

  • Retrieving specific log events based on signal IDs and custom filters.

  • Monitoring the state of alerts within the Seq system.

  • Managing and listing shared signals with detailed information.

  • Integrating Seq's API with MCP-compatible applications like Claude Desktop.

FAQ from Seq MCP Server

What environment variables are required?

SEQ_BASE_URL (optional, defaults to 'http://localhost:8080') and SEQ_API_KEY (required).

How do I install the server?

Clone the repository, then run npm run build.

How do I use this with Claude Desktop?

Add the server configuration to your claude_desktop_config.json file, specifying the command, arguments, and environment variables.

How can I debug the server?

The server implements proper error handling and logging. You can also run the test script using npm run test-script.

What time range options are available for event retrieval?

The get-events tool supports time ranges such as 1m, 15m, 30m, 1h, 2h, 6h, 12h, 1d, 7d, 14d, and 30d.