Status Observer MCP server

The Model Context Protocol (MCP) Status Observer is an integration that allows Claude Desktop to monitor and query the operational status of major digital platforms like GitHub, Slack, Discord, and more. It provides real-time status updates through a simple command interface.

Requirements

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

Installation

Installing Manually

1. Clone or download the 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

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)

Claude Desktop can automatically start the MCP server when needed:

Configuration

Edit the Claude Desktop configuration file 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

Add the Status Observer MCP configuration:

{
  "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.

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

Direct Commands:

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

Natural Language Prompts:

You can also interact with the MCP using natural language:

• "Could you check if there are any issues with Google Cloud Platform services right now?"
• "Has there been any recent issues with Claude or the Anthropic API?"
• "Is OpenAI experiencing any outages at the moment?"
• "What's the current status of LinkedIn?"
• "Pull Requests are down? What's the status of GitHub?"
• "Can you tell me if Google's Gemini AI is experiencing any service disruptions or outages right now?"
• "Check if Docker Hub Automated Builds is experiencing any outages"
• "Show me the status of all major platforms"

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.

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.