home / mcp / ai status dashboard mcp server

AI Status Dashboard MCP Server

Provides real-time AI service status monitoring, incident logging, analytics, and notifications.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "aistatusdashboard-aistatusdashboard": {
      "url": "https://aistatusdashboard.com/mcp",
      "headers": {
        "CRON_SECRET": "<CRON_SECRET>",
        "WEBHOOK_SECRET": "<WEBHOOK_SECRET>",
        "APP_CRON_SECRET": "<APP_CRON_SECRET>",
        "APP_WEBHOOK_SECRET": "<APP_WEBHOOK_SECRET>",
        "APP_ALLOW_OPEN_CRON": "<APP_ALLOW_OPEN_CRON>",
        "APP_ALLOW_PUBLIC_WEBHOOKS": "<APP_ALLOW_PUBLIC_WEBHOOKS>"
      }
    }
  }
}

You can run and interact with the AI Status Dashboard MCP server to monitor real-time AI service status, view historical data, and manage notifications. This MCP server exposes endpoints and automations to keep you informed about uptime, incidents, and performance, while integrating with your existing infrastructure.

How to use

You will connect to the MCP server using the provided MCP URL to perform status checks, subscribe to notifications, and review analytics. Use the HTTP endpoint to fetch current status, review the status history, and configure webhook or email notifications. Access to the MCP server enables you to observe real-time health signals from AI service providers and to automate incident reporting and alerting within your operations.

How to install

Prerequisites you need before installing the MCP server are Node.js 18+ and a Firebase project with Firestore enabled.

Step by step setup flow you can follow.

# 1) Clone the repository
git clone https://github.com/aistatusdashboard/aistatusdashboard
cd aistatusdashboard

# 2) Install dependencies
npm install

# 3) Copy example environment file and configure credentials
cp .env.example .env.local
# Edit .env.local to configure Firebase credentials and other settings
```
```bash
```bash
# 4) Start the development server locally
npm run dev
```
```bash
# 5) Access the app locally at http://localhost:3000 (default) and verify MCP endpoints

Additional sections

Configuration notes: You can enable production specific settings by configuring environment variables such as CRON_SECRET, APP_CRON_SECRET, WEBHOOK_SECRET, APP_WEBHOOK_SECRET and related flags like APP_ALLOW_OPEN_CRON or APP_ALLOW_PUBLIC_WEBHOOKS. Store sensitive values in Secret Manager when deploying, and grant App Hosting access as needed.

Deployment notes: For deployment with Firebase App Hosting, configure production environment variables in apphosting.yaml and store secrets in Secret Manager. Then deploy with the Firebase CLI. This ensures your MCP server runs in a managed environment with proper secret handling.

Security and troubleshooting: If you need to manage endpoint verifications for webhooks, ensure you set WEBHOOK_SECRET in production and validate incoming requests accordingly. When issues arise, check the status history in the Firestore collections and review analytics events to diagnose uptime or latency problems.