mcp-github -plus

This MCP server provides a GitHub API powered bridge with a set of file and repository management capabilities. It exposes tools to create or update files, push multiple files in a single commit (by content or from disk paths), search repositories, manage issues and pull requests, create branches, and perform code, issue, and user searches. Typical usage involves authenticating to GitHub via a token and then invoking the provided actions through the MCP gateway. For example, you can create or update a single file in a repository, push a batch of files in one commit, or programmatically search for repositories or issues across GitHub. The server ensures automatic branch creation when needed and preserves Git history without force pushes, while offering batch operations and advanced search across code, issues, PRs, and users.

Prerequisites:

• Node.js (v14+ recommended)
• npm (comes with Node.js)
• GitHub personal access token with appropriate scopes (e.g., repo, read:org) for API operations

Installation steps:

1. Install the MCP server package (example uses npm): npm install -g improved-github-mcp

2. Create a configuration file for MCP, e.g. mcp_config.json, with the server details (see mcp_config example below).

3. Ensure your environment has access to the GitHub token. You can export it in your shell or place it in the MCP config as an environment variable.

4. Start the MCP server using your preferred MCP runner (the following assumes a local Node-based server entry point named server.js): node server.js

5. Validate the server is up by invoking its API endpoints or using an MCP client that targets the configured server.

Note: If you are packaging this as a Docker/containerized service, adapt the command to your container runtime and mount the configuration as needed.

Tips and common considerations:

• Always provide a valid GitHub token with the necessary scopes for the actions you intend to perform (repos scope for most file and repo operations).
• When using batch file operations, ensure file paths and contents are correct to avoid partial commits. The server supports both direct content and filesystem path sources.
• For search capabilities, you can tailor queries to repositories, code, issues, PRs, and users to fit your workflow.
• If you encounter authentication errors, verify that the GITHUB_TOKEN is correctly loaded by the MCP runner and that the token has not expired or been revoked.
• Environment variables can be extended as needed for more advanced GitHub API interactions or to configure rate limits, timeouts, or proxies.
• When creating branches or performing operations, the server will automatically create branches if they do not exist, preserving history without force pushes.