MCP Server Inspector

Created By
vaibhavtayal6a year ago
Overview

What is MCP Server Inspector?

MCP Server Inspector is a modern React-based tool designed for testing and validating MCP (Message Control Protocol) servers.

How to use MCP Server Inspector?

To use MCP Server Inspector, clone the repository from GitHub, install the necessary dependencies, and start the development server. You can also edit files directly in GitHub or use GitHub Codespaces for a more integrated experience.

Key features of MCP Server Inspector?

  • 🔌 Server Connection Testing: Verify server availability and response times.
  • 🔑 API Authentication: Support for API key and bearer token authentication.
  • ⏱️ Performance Metrics: Measure and display response times.
  • 📋 Detailed Reporting: Comprehensive test results and server information.
  • 🧪 API Testing: Validate functionality with real-time requests.
  • 📝 Response Inspector: Examine and validate response formats.

Use cases of MCP Server Inspector?

  1. Testing the availability and performance of MCP servers.
  2. Validating API responses and ensuring they meet expected formats.
  3. Generating detailed reports for server performance metrics.

FAQ from MCP Server Inspector?

  • What technologies are used for this project?

This project is built with Vite, TypeScript, React, shadcn-ui, and Tailwind CSS.

  • How can I deploy this project?

You can deploy the project using Lovable by following the instructions provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vaibhavtayal6
Star
0
Language
TypeScript
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