Inspector Mcp Server

Created By
inspector-apm10 months ago
The Inspector MCP Server bridges the gap between AI coding assistants and production application monitoring, enabling developers to leverage AI for faster debugging and improved application reliability. Built specifically for the PHP ecosystem, this server integrates seamlessly with Inspector.dev to provide AI agents with real-time access to production error data and intelligent analysis.
Overview

What is Inspector MCP Server?

Inspector MCP Server is an AI-powered debugging and monitoring integration specifically designed for PHP applications, enabling developers to leverage AI for faster debugging and improved application reliability.

How to use Inspector MCP Server?

To use the Inspector MCP Server, install it via Composer with the command composer require inspector-apm/mcp-server --dev, and configure the MCP client with your Inspector API key and App ID.

Key features of Inspector MCP Server?

  • Smart error analysis with AI agents fetching and analyzing recent production errors.
  • Intelligent prioritization of errors based on frequency, severity, and recency.
  • Actionable recommendations for root cause analysis and resolution strategies.
  • Code-level insights with direct integration to stack traces and application source code.

Use cases of Inspector MCP Server?

  1. Assisting PHP developers in debugging modern applications with AI support.
  2. Providing intelligent error analysis for teams using Inspector.dev for production monitoring.
  3. Enhancing the development workflow for users of the Neuron AI framework.
  4. Supporting DevOps engineers in identifying and resolving application errors efficiently.

FAQ from Inspector MCP Server?

  • What programming language does it support?

Inspector MCP Server is built specifically for the PHP ecosystem.

  • Is it easy to integrate with existing applications?

Yes! It is designed for seamless integration with modern PHP development workflows.

  • Can it help with real-time error monitoring?

Absolutely! It provides real-time access to production error data and intelligent analysis.

Server Config

{
  "mcpServers": {
    "inspector": {
      "command": "php",
      "args": [
        "absolute-path-to-your-app-vendor-folder/inspector-apm/mcp-server/server.php"
      ],
      "env": {
        "INSPECTOR_API_KEY": "xxxx",
        "INSPECTOR_APP_ID": "xxxx"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
9 months ago
Author Name
inspector-apm
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago