Get the FREE Ultimate OpenClaw Setup Guide →

mcp -seq

MCP server from ahmad2x4/mcp-server-seq

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio ahmad2x4-mcp-server-seq node /Users/ahmadreza/source/ahmad2x4/mcp-server-seq/build/seq-server.js \
  --env SEQ_API_KEY="your-api-key" \
  --env SEQ_BASE_URL="your-seq-url"

How to use

This Seq MCP Server exposes access to Seq's API features through the MCP interface, enabling you to manage signals, events, and alert states, as well as list signals in a structured way. The server parses requests for operations like get-signals, get-events, get-alertstate, and signals (listing signals with detailed metadata). You can integrate with Claude Desktop by adding the seq MCP server configuration to your claude_desktop_config.json, supplying the Seq base URL and API key via environment variables. Use the provided environment variables to securely connect to your Seq instance and authenticate requests. Time range options for events are supported to filter results over common windows such as last 1 minute up to last 30 days.

How to install

Prerequisites:

  • Node.js and npm installed on your machine
  • Access to the repository containing the MCP server (this Seq MCP server)

Installation steps:

  1. Clone the repository: git clone <repository-url>
  2. Navigate into the project directory: cd mcp-server-seq
  3. Install dependencies: npm install
  4. Build the server (if applicable): npm run build
  5. Run the server locally (example using the built file): node build/seq-server.js

If you plan to use Claude Desktop integration, ensure you configure the environment variables (SEQ_BASE_URL and SEQ_API_KEY) as described in the usage section and the README.

Additional notes

Tips and considerations:

  • Ensure SEQ_BASE_URL is reachable from where you run the MCP server; the default is http://localhost:8080 if not specified.
  • SEQ_API_KEY is required for authentication with Seq.
  • The server exposes tools like get-signals, get-events, get-alertstate, and signals listing; you can filter and query with provided options in each tool.
  • Time range options for get-events include 1m, 15m, 30m, 1h, 2h, 6h, 12h, 1d, 7d, 14d, 30d.
  • Debugging: MCP servers communicate over stdio; check log output for errors and ensure proper JSON formatting in requests.
  • This project appears to be in development and may not yet be published to npm; the README notes npm publishing is not available yet.

Related MCP Servers

Sponsor this space

Reach thousands of developers