Easy MCP GitHub Tools Application

Created By
ground-creativea year ago
A set of powerful tools designed for seamless integration with GitHub via MCP
Overview

What is Easy MCP GitHub Tools Application?

Easy MCP GitHub Tools Application is a set of powerful tools designed for seamless integration with GitHub via MCP, allowing users to manage repositories, issues, and pull requests efficiently.

How to use Easy MCP GitHub Tools Application?

To use this application, you need to create an OAuth application on GitHub, authenticate using the provided endpoint, and then make API calls with the required parameters.

Key features of Easy MCP GitHub Tools Application?

  • Branch Management: Create and delete branches in GitHub repositories.
  • Issue Tracking: Manage issues and comments.
  • Commit History: Fetch detailed commit information.
  • File Management: Create, update, and delete files.
  • Pull Requests: Manage pull requests.
  • Global Search: Perform searches across GitHub.
  • Release Management: Manage releases.
  • OAuth Authentication: Secure user authentication.

Use cases of Easy MCP GitHub Tools Application?

  1. Managing multiple GitHub repositories efficiently.
  2. Automating issue tracking and resolution.
  3. Facilitating collaboration through pull requests.
  4. Performing bulk operations on files and branches.

FAQ from Easy MCP GitHub Tools Application?

  • How do I authenticate?

You need to create an OAuth application on GitHub and use the provided authentication endpoint.

  • Is there a limit on API calls?

Yes, GitHub has rate limits for API calls based on the type of authentication used.

  • Can I use this with any GitHub repository?

Yes, as long as you have the necessary permissions for the repository.

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