mcptesting

Created By
AndreaGriffiths11a year ago
Test repository created via MCP server
Overview

what is mcptesting?

mcptesting is a test repository created via the MCP server, designed for testing purposes and collaboration among developers.

how to use mcptesting?

To use mcptesting, clone the repository from GitHub and start testing your applications or features using the provided resources.

key features of mcptesting?

  • Easy access to a test repository for developers.
  • Collaboration tools for team members.
  • Integration with MCP server for streamlined testing.

use cases of mcptesting?

  1. Testing new features in a controlled environment.
  2. Collaborating with team members on testing strategies.
  3. Utilizing the repository for continuous integration and deployment processes.

FAQ from mcptesting?

  • Is mcptesting open for contributions?

Yes! Developers are encouraged to contribute to the repository.

  • How can I report issues with mcptesting?

You can report issues directly on the GitHub repository's issue tracker.

  • Is there any documentation available for mcptesting?

Yes, documentation can be found in the repository's README file.

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