Test d'intégration MCP Server GitHub

Created By
Erkkula year ago
Référentiel de test pour l'intégration MCP server GitHub
Overview

What is MCP Server Test?

MCP Server Test is a repository designed for testing the integration with the MCP server on GitHub.

How to use MCP Server Test?

To use MCP Server Test, clone the repository from GitHub and run the integration tests to verify that all GitHub operations can be performed through the MCP server.

Key features of MCP Server Test?

  • Integration testing for GitHub operations
  • Easy setup and execution of tests
  • Supports various GitHub functionalities

Use cases of MCP Server Test?

  1. Verifying the functionality of GitHub API calls through the MCP server.
  2. Ensuring that all GitHub operations are compatible with the MCP server.
  3. Testing new features or updates in the MCP server integration.

FAQ from MCP Server Test?

  • What programming language is used in this project?

The project is developed in Python.

  • Is this repository official?

No, this repository is not an official project.

  • How can I contribute to this project?

You can contribute by submitting issues or pull requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Erkkul
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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