GitHub MCP Server

Created By
minimind-orga year ago
MCP server for github operation
Overview

What is GitHub MCP Server?

GitHub MCP Server is a server designed to facilitate operations with the GitHub API, enabling users to perform file operations, manage repositories, and execute advanced search functionalities.

How to use GitHub MCP Server?

To use the GitHub MCP Server, you need to set up a Personal Access Token from GitHub and configure it in your environment. You can run the server using Docker or NPX commands as specified in the setup instructions.

Key features of GitHub MCP Server?

  • Automatic branch creation for file operations.
  • Comprehensive error handling with clear messages.
  • Preservation of Git history during operations.
  • Support for batch operations on multiple files.
  • Advanced search capabilities for repositories, code, issues, and users.

Use cases of GitHub MCP Server?

  1. Automating repository management tasks.
  2. Performing bulk file updates in a repository.
  3. Searching for specific code snippets or issues across multiple repositories.

FAQ from GitHub MCP Server?

  • What is a Personal Access Token?

A Personal Access Token is a secure way to authenticate with GitHub's API, allowing you to perform actions on your repositories.

  • Can I use this server for private repositories?

Yes, you can configure the server to access private repositories by setting the appropriate permissions on your Personal Access Token.

  • Is there a limit to the number of files I can push at once?

The server supports batch operations, but the maximum number of files may depend on GitHub's API rate limits.

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

20 hours ago
Gpt Scrambler

2 days ago