GitHub MCP Server

Created By
peterparker57a year ago
GitHub MCP server with enhanced file management capabilities
Overview

what is GitHub MCP Server?

GitHub MCP Server is a Model Context Protocol (MCP) server that provides enhanced file management capabilities for GitHub integration, allowing users to interact with GitHub repositories through various operations.

how to use GitHub MCP Server?

To use the GitHub MCP Server, install it via npm and configure it in your MCP settings file. You can then perform operations like repository management and file handling through the provided tools.

key features of GitHub MCP Server?

  • Account management and authentication
  • Repository creation and management
  • File operations (read, write, push, pull)
  • Commit operations
  • Directory synchronization
  • Repository comparison and diffing

use cases of GitHub MCP Server?

  1. Managing multiple GitHub repositories efficiently.
  2. Automating file operations between local and remote repositories.
  3. Synchronizing directories for collaborative projects.

FAQ from GitHub MCP Server?

  • Can I manage multiple GitHub accounts?

Yes! You can configure multiple accounts by adding them to your MCP settings.

  • Is there a way to automate commits?

Yes! The server allows you to create commits with multiple file changes programmatically.

  • What programming languages are supported?

The server is built with TypeScript and can be used in any environment that supports Node.js.

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