Overview - Middleware MCP Server
The Middleware MCP Server is a remote Model Context Protocol (MCP) server that lets AI assistants and agentic IDEs, such as Claude Code, Claude Desktop, Cursor, and VS Code, work with your Middleware observability data using natural language.
Instead of switching between your editor and the Middleware UI, you can ask your assistant to "list my dashboards", "show me errors from the last hour", or "query CPU usage for the checkout service", and it calls Middleware for you and returns the result.
The server is hosted by Middleware and available at a single endpoint:
https://mcp.middleware.io/mcpYou point a supported client at this URL, sign in to your Middleware account once in the browser, and your assistant gains access to the Middleware tools.
Connect a client#
Ready to get started? Select your client to jump to its setup steps, or see Setup for the prerequisites and how sign-in works.
How it works#
In MCP, the server exposes a set of tools. Each tool has a name and a typed input schema, so the assistant's calls stay structured and predictable.
When your client invokes a tool, the server authenticates the request with your access token, routes it to the project you selected during sign-in, calls the matching Middleware API, and returns the result. You only ever see your own data.
What your assistant can do#
The server exposes 19 tools across four areas:
- Dashboards — list, read, create, update, delete, clone, and favorite dashboards.
- Widgets — list, create, update, delete, fetch data, and adjust layout.
- Metrics and resources — discover metrics and resources, and run queries for logs, metrics, and traces.
- Error tracking — list errors and incidents and read their details.
For the full list with each tool's inputs and behavior, see MCP Tools.
Need assistance or want to learn more about Middleware? Contact our support team at [email protected] or join our Slack channel.