mcp-test-servers

Created By
mjg7822a year ago
Overview

what is mcp-test-servers?

The mcp-test-servers project is designed to facilitate the management and automation of test servers for various applications.

how to use mcp-test-servers?

To use mcp-test-servers, clone the repository from GitHub and follow the setup instructions provided in the README file to configure your test environment.

key features of mcp-test-servers?

  • Automated setup and teardown of test servers
  • Support for multiple testing environments
  • Integration with CI/CD pipelines for seamless testing

use cases of mcp-test-servers?

  1. Setting up isolated environments for running automated tests.
  2. Managing multiple test configurations for different applications.
  3. Integrating with existing development workflows to enhance testing efficiency.

FAQ from mcp-test-servers?

  • What programming languages does mcp-test-servers support?

The project is designed to be language-agnostic and can be used with any programming language that supports server management.

  • Is there any documentation available?

Yes! Comprehensive documentation is available in the GitHub repository.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and you can find guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mjg7822
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)

2 days ago