MCP Tool for GitHub

Created By
jalaj-pandeya year ago
A dedicated MCP (Model Context Protocol) tool for github, The MCP (Model Context Protocol) Tool for GitHub is a Python-based solution designed to help manage and track machine learning model context directly within GitHub repositories.
Overview

What is MCP Tool for GitHub?

The MCP (Model Context Protocol) Tool for GitHub is a Python-based solution designed to help manage and track machine learning model context directly within GitHub repositories.

How to use MCP Tool for GitHub?

To use the MCP Tool, clone the repository from GitHub, install the required dependencies, and follow the setup instructions to initialize the tool.

Key features of MCP Tool for GitHub?

  • Track model versions
  • Manage dataset information
  • Record performance metrics
  • Document training configurations
  • Seamless GitHub integration

Use cases of MCP Tool for GitHub?

  1. Documenting machine learning model versions in a collaborative environment.
  2. Keeping track of datasets and their associated metrics for reproducibility.
  3. Managing training configurations for different model experiments.

FAQ from MCP Tool for GitHub?

  • What programming language is MCP Tool written in?

MCP Tool is written in Python.

  • Is there a specific version of Python required?

Yes, Python 3.7 or higher is required.

  • How do I install the MCP Tool?

You can install it by cloning the repository and running pip install -r requirements.txt.

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