Get the FREE Ultimate OpenClaw Setup Guide →

mcp-status-observer

Model Context Protocol server for monitoring Operational Status of major digital platforms in Claude Desktop.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio imprvhub-mcp-status-observer node ABSOLUTE_PATH_TO_DIRECTORY/mcp-status-observer/build/index.js

How to use

The MCP Status Observer is an integration that lets Claude Desktop monitor and query the operational status of major digital platforms, including AI providers, cloud services, and developer tools, using the Model Context Protocol (MCP). It exposes a single tool named status with commands to list platforms, query a specific platform, or fetch full status across all platforms. Install and run the server, then interact with it through Claude Desktop by issuing commands like status list, status --openrouter, or status --all to retrieve real-time status data and incident histories for the supported services.

How to install

Prerequisites:

  • Node.js 16 or higher
  • npm (comes with Node.js)
  • Claude Desktop (for automatic startup) or manual running environment

Installation steps:

  1. Clone the repository: git clone https://github.com/imprvhub/mcp-status-observer cd mcp-status-observer

  2. Install dependencies: npm install

  3. Build the project (produces build/index.js): npm run build

  4. Run manually (optional for testing): node build/index.js

  5. Configure Claude Desktop to manage the MCP server (example configuration): { "mcpServers": { "statusObserver": { "command": "node", "args": ["ABSOLUTE_PATH_TO_DIRECTORY/mcp-status-observer/build/index.js"] } } } Replace ABSOLUTE_PATH_TO_DIRECTORY with the full path to your cloned repository.

  6. Restart Claude Desktop and use the status tool to interact with the MCP server.

Additional notes

Tips and common issues:

  • Ensure you build before trying to run via Claude Desktop; the server entry point is build/index.js.
  • When configuring Claude Desktop, always use the absolute path to the build/index.js file.
  • If the server doesn’t start, check Node.js compatibility and ensure dependencies are installed (npm install).
  • The MCP server exposes a single command: status. Use subcommands like status list, status --<platform>, or status --all to fetch data.
  • If platforms are missing after an update, run npm run build to refresh the MCP integrations.
  • For manual runs, keep the terminal open as the MCP server runs as a foreground process.

Related MCP Servers

Sponsor this space

Reach thousands of developers