mcp-server-test

Created By
raphael-shina year ago
MCP Server Test Repository
Overview

what is MCP Server Test?

MCP Server Test is a repository designed for testing purposes related to the MCP server framework.

how to use MCP Server Test?

To use MCP Server Test, clone the repository from GitHub and follow the instructions in the README file to set up your testing environment.

key features of MCP Server Test?

  • Provides a structured environment for testing MCP server functionalities.
  • Easy setup and configuration for developers.
  • Supports various testing scenarios for server performance and reliability.

use cases of MCP Server Test?

  1. Testing server response times under different loads.
  2. Validating server configurations and settings.
  3. Ensuring compatibility with various client applications.

FAQ from MCP Server Test?

  • What is the purpose of this repository?

The repository is intended for developers to test and validate MCP server functionalities.

  • Is there documentation available?

Yes, documentation is provided in the README file of the repository.

  • Can I contribute to this project?

Yes, contributions are welcome! Please follow the contribution guidelines in the repository.

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