GitHub MCP Server

Created By
PoliTwit1984a year ago
An MCP server that enables natural language commands for managing GitHub repositories
Overview

what is GitHub MCP Server?

GitHub MCP Server is a Model Context Protocol (MCP) server that enables users to manage GitHub repositories using natural language commands, simplifying the interaction with GitHub's API.

how to use GitHub MCP Server?

To use the GitHub MCP Server, clone the repository, install the dependencies, and configure it with your GitHub personal access token. You can then use natural language commands to create or update repositories.

key features of GitHub MCP Server?

  • Create GitHub repositories with auto-generated names from descriptions.
  • Add topics/tags to repositories.
  • Set repository homepages.
  • Auto-initialize repositories with README files.
  • Supports natural language commands for repository management.

use cases of GitHub MCP Server?

  1. Quickly creating new repositories for projects without manual setup.
  2. Updating repository details using simple commands.
  3. Managing multiple repositories efficiently through natural language.

FAQ from GitHub MCP Server?

  • Can I use any natural language command?

Yes! The server is designed to understand various natural language patterns for creating and updating repositories.

  • Do I need a GitHub account to use this server?

Yes! You need a GitHub account and a personal access token with repository creation permissions.

  • Is there any limit on the number of repositories I can create?

There are limits set by GitHub on repository creation, but the server itself does not impose additional limits.

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

Recommend Servers

View All
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

a day ago