Middleware MCP Server

A robust and modular Model Context Protocol (MCP) server for Middleware.io. This server enables AI assistants like Claude to interact with Middleware's observability platform for monitoring, dashboards, widgets, metrics, and alerts.
---
⚠️ This repository is archived
**This self-hosted MCP server is no longer actively maintained.** Middleware now offers a
**hosted remote MCP server** that requires no build step, no API key management, and no local
process to keep running — and it ships more tools than this repository.
👉 **Use the remote MCP server instead:** https://mcp.middleware.io/mcp
📚 **Docs:** Middleware MCP Server overview
Why move to the remote server?
| | Remote MCP server (recommended) | This repo (archived) |
|---|---|---|
| Setup | One-line client config | Clone, install Go, build, configure .env |
| Auth | Browser sign-in (OAuth), token handled for you | Manually manage MIDDLEWARE_API_KEY |
| Project selection | Pick your project during authorization | Hardcoded via MIDDLEWARE_BASE_URL |
| Tools | 24 tools (incl. **Logs** and **RUM**) | 21 tools |
| Updates | Automatic, server-side | You rebuild and redeploy |
| Runtime | Nothing to run locally | Local binary per machine |
Connect the remote server
All clients point at the same endpoint: https://mcp.middleware.io/mcp
**Claude Code**
Then run /mcp, select **middleware**, and choose **Authenticate**.
**Claude Desktop** — add to ~/.claude.json:
**Cursor** — add to ~/.cursor/mcp.json (or project-level .cursor/mcp.json):
**VS Code** — add to .vscode/mcp.json (or use **MCP: Add Server → HTTP** from the Command Palette):
**Windsurf** — add to ~/.codeium/windsurf/mcp_config.json:
**Gemini CLI**
**Codex CLI**
Other MCP-compatible clients (Antigravity and anything supporting remote HTTP servers with OAuth)
work the same way — point them at the endpoint URL.
**Authentication flow:** configure the endpoint → your client opens a browser → sign in to
Middleware → pick the project → approve access. The sign-in persists across sessions, so you only
do this once.
**Read-only access:** append exclude_tools to the URL to strip out write operations, e.g.
See Setup and
MCP Tools for the full reference.
---
> The rest of this README documents the archived self-hosted server. It is kept for reference and
> for anyone who must run the server inside their own network. New integrations should use the
> remote MCP server above.
Available Tools (self-hosted, archived)
_The remote MCP server exposes these plus Logs and RUM tools — see MCP Tools._
Dashboard Management (7 tools)
- list_dashboards - List all dashboards with filtering and pagination
- get_dashboard - Get a specific dashboard by key
- create_dashboard - Create a new dashboard
- update_dashboard - Update an existing dashboard
- delete_dashboard - Delete a dashboard
- clone_dashboard - Clone an existing dashboard
- set_dashboard_favorite - Mark dashboard as favorite/unfavorite
Widget Management (6 tools)
- list_widgets - List widgets for a report or display scope
- create_widget - Create or update a widget
- delete_widget - Delete a widget
- get_widget_data - Get data for a specific widget
- get_multi_widget_data - Get data for multiple widgets at once
- update_widget_layouts - Update widget layout positions
Metrics & Resources (3 tools)
- get_metrics - Get metrics, filters, or groupby tags
- get_resources - Get available resources for queries
- query - Execute flexible queries to retrieve logs, metrics, traces, and other data
Alerts (3 tools)
- list_alerts - List alerts for a specific rule
- create_alert - Create a new alert
- get_alert_stats - Get alert statistics
Error/Incident Management (2 tools)
- list_errors - List all errors/incidents with filtering and pagination (includes clickable issue_url for each incident)
- get_error_details - Get detailed information about a specific error/incident by fingerprint
Quick Start (self-hosted, archived)
Get up and running in 5 minutes. **For new setups, prefer the remote MCP server — it needs none of these steps.**