GitHub MCP Server Plus

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is GitHub MCP Server Plus?

GitHub MCP Server Plus is a server that interacts with the GitHub API, enabling various file operations, repository management, and advanced search functionalities.

how to use GitHub MCP Server Plus?

To use the server, set up a GitHub Personal Access Token with the necessary permissions and configure it with either Docker or NPX as per the provided instructions.

key features of GitHub MCP Server Plus?

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

use cases of GitHub MCP Server Plus?

  1. Managing multiple repositories efficiently.
  2. Automating file updates and branch management.
  3. Conducting advanced searches for code and issues across repositories.

FAQ from GitHub MCP Server Plus?

  • What is a Personal Access Token?

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

  • Can I use this server for private repositories?

Yes, as long as your Personal Access Token has the appropriate permissions.

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

The server supports batch operations, but GitHub API limits may apply.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Alloy

2 days 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)

8 hours ago
Crevio

a day ago