MCP_testing_server

Created By
githuba year ago
Overview

What is GitHub MCP Server?

The GitHub MCP Server is a Model Context Protocol (MCP) server that integrates with GitHub APIs, enabling advanced automation and interaction capabilities for developers and tools.

How to use GitHub MCP Server?

To use the GitHub MCP Server, you need to install Docker and create a GitHub Personal Access Token. You can then run the server using Docker or build it from source.

Key features of GitHub MCP Server?

  • Seamless integration with GitHub APIs for automation.
  • Support for various GitHub functionalities like issues, pull requests, and repositories.
  • Dynamic tool discovery and customizable toolsets.

Use cases of GitHub MCP Server?

  1. Automating GitHub workflows and processes.
  2. Extracting and analyzing data from GitHub repositories.
  3. Building AI-powered tools that interact with GitHub's ecosystem.

FAQ from GitHub MCP Server?

  • Can I use GitHub MCP Server without Docker?

Yes, you can build it from source using Go.

  • Is there a way to customize the functionalities?

Yes, you can enable or disable specific toolsets using command line arguments or environment variables.

  • What permissions do I need for the GitHub Personal Access Token?

Enable permissions based on the functionalities you want to use with the MCP server.

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