MCP.so
Sign In

MCP Servers

@Dienvm

About MCP Servers

Repository for MCP servers configuration and setup

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-servers-dienvm": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-github"
      ]
    }
  }
}

Tools

26

Create or update a single file in a GitHub repository

Search for GitHub repositories

Create a new GitHub repository in your account

Get the contents of a file or directory from a GitHub repository

Push multiple files to a GitHub repository in a single commit

Create a new issue in a GitHub repository

Create a new pull request in a GitHub repository

Fork a GitHub repository to your account or specified organization

Create a new branch in a GitHub repository

Get list of commits of a branch in a GitHub repository

List issues in a GitHub repository with filtering options

Update an existing issue in a GitHub repository

Add a comment to an existing issue

Search for code across GitHub repositories

Search for issues and pull requests across GitHub repositories

Search for users on GitHub

Get details of a specific issue in a GitHub repository.

Get details of a specific pull request

List and filter repository pull requests

Create a review on a pull request

Merge a pull request

Get the list of files changed in a pull request

Get the combined status of all status checks for a pull request

Update a pull request branch with the latest changes from the base branch

Get the review comments on a pull request

Get the reviews on a pull request

Overview

What is MCP Servers?

MCP Servers is a repository containing configuration and setup for Model Context Protocol (MCP) servers, specifically providing GitHub API integration (via server-github) and web browser automation (via server-puppeteer). It is intended for developers who want to integrate these services with MCP-compatible clients.

How to use MCP Servers?

Install the required server packages using npx commands (e.g., npx -y @modelcontextprotocol/server-github and npx -y @modelcontextprotocol/server-puppeteer). Configure them in a JSON structure under mcpServers, setting the GITHUB_PERSONAL_ACCESS_TOKEN environment variable for the GitHub server. Run each server directly with the appropriate token, e.g., GITHUB_PERSONAL_ACCESS_TOKEN="your-token" npx -y @modelcontextprotocol/server-github.

Key features of MCP Servers

  • GitHub integration: repository management, issue tracking, pull request handling, and code search.
  • Puppeteer integration: web automation, screenshot capture, page navigation, and form interaction.
  • Supports both server packages through a unified MCP configuration structure.
  • Each server is installed and run via npx with minimal setup.
  • MIT licensed and open to contributions.

Use cases of MCP Servers

  • Manage GitHub repositories, issues, and pull requests programmatically through an MCP client.
  • Search code across repositories within the GitHub ecosystem.
  • Automate web interactions, such as filling forms or navigating pages, via Puppeteer.
  • Capture screenshots of web pages for testing or monitoring purposes.
  • Integrate GitHub and browser automation capabilities into AI assistants or other MCP‑compatible tools.

FAQ from MCP Servers

What is the difference between the GitHub and Puppeteer MCP servers?

The GitHub MCP server interacts with the GitHub API for repository management and issue tracking, while the Puppeteer MCP server automates web browsers for tasks like navigation and screenshots.

What are the runtime dependencies for MCP Servers?

Node.js and npm are required. The GitHub MCP server additionally needs a GitHub Personal Access Token.

Where does data from MCP Servers live?

Data is handled externally: the GitHub server retrieves data from the GitHub API, and the Puppeteer server operates on live web content via a browser instance.

How is authentication handled?

The GitHub MCP server uses a GITHUB_PERSONAL_ACCESS_TOKEN environment variable. The Puppeteer server does not require authentication.

Are there any known limits?

The README does not specify any limits beyond the capabilities of the underlying GitHub API and Puppeteer.

What transport does the server use?

The README does not specify the transport protocol; it only describes the configuration structure for MCP integration.

Frequently asked questions

What is the difference between the GitHub and Puppeteer MCP servers?

The GitHub MCP server interacts with the GitHub API for repository management and issue tracking, while the Puppeteer MCP server automates web browsers for tasks like navigation and screenshots.

What are the runtime dependencies for MCP Servers?

Node.js and npm are required. The GitHub MCP server additionally needs a GitHub Personal Access Token.

Where does data from MCP Servers live?

Data is handled externally: the GitHub server retrieves data from the GitHub API, and the Puppeteer server operates on live web content via a browser instance.

How is authentication handled?

The GitHub MCP server uses a `GITHUB_PERSONAL_ACCESS_TOKEN` environment variable. The Puppeteer server does not require authentication.

Are there any known limits?

The README does not specify any limits beyond the capabilities of the underlying GitHub API and Puppeteer.

What transport does the server use?

The README does not specify the transport protocol; it only describes the configuration structure for MCP integration.

Comments

More Other MCP servers