GitHub MCP Server

Created By
Joseph19820124a year ago
A GitHub MCP server demo with create repository functionality
Overview

what is GitHub MCP Server?

GitHub MCP Server is a Model Context Protocol (MCP) server that provides functionality for managing GitHub repositories, including the ability to create new repositories with customizable settings.

how to use GitHub MCP Server?

To use the GitHub MCP Server, clone the repository, install the required dependencies, set up your GitHub Personal Access Token, and run the server using Python.

key features of GitHub MCP Server?

  • Create new GitHub repositories with customizable settings.
  • Supports JSON-RPC 2.0 for communication.
  • Implements the Model Context Protocol for connecting AI applications with external data sources.

use cases of GitHub MCP Server?

  1. Automating the creation of GitHub repositories for projects.
  2. Integrating with AI applications to manage repositories dynamically.
  3. Facilitating repository management in development workflows.

FAQ from GitHub MCP Server?

  • What is required to run the GitHub MCP Server?

You need Python 3.8 or higher and a GitHub Personal Access Token with repository creation permissions.

  • How do I create a new repository using the server?

You can send a JSON-RPC request to the create_repository tool with the required parameters.

  • Is there any documentation available?

Yes, the README file in the repository contains detailed instructions on installation, usage, and available tools.

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