🚫 MCP GIT: Server Testing 🚫

Created By
gkushanga year ago
🚀 Where code meets imagination! ✨
Overview

What is MCP GIT: Server Testing?

MCP GIT: Server Testing is a testing repository designed to evaluate the functionality of the MCP Github Server, showcasing various operations related to repository management.

How to use MCP GIT: Server Testing?

To use this repository, clone it from GitHub and explore the various features tested, such as repository creation and file management, by interacting with the GitHub API.

Key features of MCP GIT: Server Testing?

  • Repository creation and management
  • File uploads and content modifications
  • API integration with GitHub REST API
  • Authentication using Personal Access Tokens (PAT)

Use cases of MCP GIT: Server Testing?

  1. Testing repository creation and file management workflows.
  2. Evaluating API responses and handling JSON data.
  3. Demonstrating communication with GitHub's API for various operations.

FAQ from MCP GIT: Server Testing?

  • Is this repository open for contributions?

No, this is a test repository and does not require contributions.

  • What is the purpose of this repository?

It is created to test the MCP GIT: Server functionality and demonstrate various features.

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