MCP Status Observer

MCP Status Observer

An integration that allows Claude Desktop to monitor and query the operational status of major digital platforms using the Model Context Protocol (MCP).

Features

• Monitor world's most used digital platforms (GitHub, Slack, Discord, etc.)
• Get detailed status information for specific services
• Check status of specific components within each platform
• Simple query interface with commands like status --github.
• Real-time updates of service status

Demo

Click on any timestamp to jump to that section of the video

00:00 - LinkedIn Platform Status Assessment Comprehensive analysis of LinkedIn's operational health, including detailed examination of core services such as LinkedIn.com, LinkedIn Learning, Campaign Manager, Sales Navigator, Recruiter, and Talent solutions. All systems confirmed fully operational with zero service disruptions.

00:20 - GitHub Infrastructure Status Overview Detailed evaluation of GitHub's service availability, covering critical components including Git operations, API requests, Actions, Webhooks, Issues, Pull Requests, Packages, Pages, Codespaces, and Copilot functionality. Complete operational status confirmed across all GitHub services.

00:40 - Vercel Platform Reliability Analysis In-depth examination of Vercel's global edge network and deployment infrastructure, featuring comprehensive status reporting on core services such as API, Dashboard, Builds, Serverless Functions, Edge Functions, and global CDN locations. All Vercel services verified operational across all regions.

01:08 - Cloudflare Network Status Examination Extensive analysis of Cloudflare's global infrastructure status, detailing service availability across geographic regions and specific service components. Identified performance degradation in multiple regions (Africa, Asia, Europe, Latin America, Middle East, North America) while core services remain functional. Includes detailed assessment of regional data centers under maintenance and technical impact analysis.

01:46 - Global Operational Status Report Consolidated overview of operational status across all major technology platforms and service providers, highlighting both fully operational services (GitHub, Vercel, Netlify, Asana, Atlassian, etc.) and services experiencing degraded performance (Cloudflare, Twilio). Includes strategic recommendations for organizations with dependencies on affected services.

Requirements

• Node.js 16 or higher
• Claude Desktop
• Internet connection to access status APIs

Installation

Installing Manually

1. Clone or download this repository:

git clone https://github.com/imprvhub/mcp-status-observer
cd mcp-status-observer

2. Install dependencies:

npm install

3. Build the project:

npm run build

Running the MCP Server

There are two ways to run the MCP server:

Option 1: Running manually

1. Open a terminal or command prompt
2. Navigate to the project directory
3. Run the server directly:

node build/index.js

Keep this terminal window open while using Claude Desktop. The server will run until you close the terminal.

Option 2: Auto-starting with Claude Desktop (recommended for regular use)

The Claude Desktop can automatically start the MCP server when needed. To set this up:

Configuration

The Claude Desktop configuration file is located at:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Edit this file to add the Status Observer MCP configuration. If the file doesn't exist, create it:

{
  "mcpServers": {
    "statusObserver": {
      "command": "node",
      "args": ["ABSOLUTE_PATH_TO_DIRECTORY/mcp-status-observer/build/index.js"]
    }
  }
}

Important: Replace ABSOLUTE_PATH_TO_DIRECTORY with the complete absolute path where you installed the MCP

• macOS/Linux example: /Users/username/mcp-status-observer
• Windows example: C:\\Users\\username\\mcp-status-observer

If you already have other MCPs configured, simply add the "statusObserver" section inside the "mcpServers" object. Here's an example of a configuration with multiple MCPs:

{
  "mcpServers": {
    "otherMcp1": {
      "command": "...",
      "args": ["..."]
    },
    "otherMcp2": {
      "command": "...",
      "args": ["..."]
    },
    "statusObserver": {
      "command": "node",
      "args": [
        "ABSOLUTE_PATH_TO_DIRECTORY/mcp-status-observer/build/index.js"
      ]
    }
  }
}

The MCP server will automatically start when Claude Desktop needs it, based on the configuration in your claude_desktop_config.json file.

Usage

1. Restart Claude Desktop after modifying the configuration
2. In Claude, use the status command to interact with the Status Observer MCP Server
3. The MCP server runs as a subprocess managed by Claude Desktop

Available Commands

The Status Observer MCP provides a single tool named status with several commands:

Example Usage

Here are various examples of how to use the Status Observer with Claude:

Direct Commands:

status --all
status --amplitude
status --asana
status --atlassian
status --cloudflare
status --digitalocean
status --discord
status --dropbox
status --gcp
status --github
status --linkedin
status --netlify
status --npm
status --reddit
status --slack
status --twilio
status --vercel
status --x
status list

Preview

Natural Language Queries:

You can also interact with the MCP using natural language. Claude will interpret these requests and use the appropriate commands:

• "What's the current status of LinkedIn?"
• "Pull Requests are down? What's the status of GitHub?"
• "Show me the status of all major platforms"
• "Could you check if there are any issues with Google Cloud Platform services right now?"

Troubleshooting

"Server disconnected" error

If you see the error "MCP Status Observer: Server disconnected" in Claude Desktop:

1. Verify the server is running:

   • Open a terminal and manually run node build/index.js from the project directory
   • If the server starts successfully, use Claude while keeping this terminal open

2. Check your configuration:

   • Ensure the absolute path in claude_desktop_config.json is correct for your system
   • Double-check that you've used double backslashes (\\) for Windows paths
   • Verify you're using the complete path from the root of your filesystem

Tools not appearing in Claude

If the Status Observer tools don't appear in Claude:

• Make sure you've restarted Claude Desktop after configuration
• Check the Claude Desktop logs for any MCP communication errors
• Ensure the MCP server process is running (run it manually to confirm)
• Verify that the MCP server is correctly registered in the Claude Desktop MCP registry

Checking if the server is running

To check if the server is running:

• Windows: Open Task Manager, go to the "Details" tab, and look for "node.exe"
• macOS/Linux: Open Terminal and run ps aux | grep node

If you don't see the server running, start it manually or use the auto-start method.

Contributing

Adding New Status APIs

Contributors can easily add support for additional platforms by modifying the initializePlatforms method in src/index.ts. The process is straightforward:

1. Identify a platform's status API endpoint
2. Add a new entry using the addPlatform method with the following parameters:
   • id: A unique identifier for the platform (lowercase, no spaces)
   • name: The display name of the platform
   • url: The status API endpoint URL
   • description: A brief description of the platform

Example:

this.addPlatform('newservice', 'New Service', 'https://status.newservice.com/api/v2/summary.json', 'Description of the service');

Different status APIs may return data in different formats. If a new platform's API returns data in a format that isn't handled by the existing code, you might need to add specific parsing logic for that platform.

License

This project is licensed under the Mozilla Public License 2.0 - see the LICENSE file for details.

Related Links

• Model Context Protocol
• Claude Desktop