MCP Server Tester

Created By
r-huijtsa year ago
Automated testing tool for Model Context Protocol (MCP) servers - WORK IN PROGRESS
Overview

What is MCP Server Tester?

MCP Server Tester is an automated testing tool designed for Model Context Protocol (MCP) servers, aimed at validating, benchmarking, and ensuring the reliability of these servers that integrate with AI models like Claude.

How to use MCP Server Tester?

To use MCP Server Tester, clone the repository, install dependencies, set up your configuration file, and run the tests using the command line. You can specify a custom configuration file if needed.

Key features of MCP Server Tester?

  • Automatically discovers available tools from any MCP server.
  • Generates realistic test cases for each tool using Claude AI.
  • Executes tests and validates responses against expected outcomes.
  • Provides detailed test reports in multiple formats (console, JSON, HTML).
  • Configuration-based usage for easy reusability and version control.

Use cases of MCP Server Tester?

  1. Validating the functionality of MCP servers during development.
  2. Benchmarking performance and reliability of AI model integrations.
  3. Ensuring compliance with MCP protocol specifications.

FAQ from MCP Server Tester?

  • Is MCP Server Tester stable for production use?

No, it is currently a work in progress and should be used in non-production environments only.

  • How do I contribute to the project?

You can contribute by opening issues and submitting pull requests on the GitHub repository.

  • What are the prerequisites for using MCP Server Tester?

You need Node.js 18 or higher and an Anthropic API key for generating test cases.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
r-huijts
Star
1
Language
TypeScript
License
MIT 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)

2 days ago
Voyei

4 hours ago