GitHub API MCP Server

Created By
HuangZeLinCutea year ago
This is github search MCP Server
Overview

What is GitHub API MCP Server?

GitHub API MCP Server is a project designed to facilitate GitHub search API operations through a managed command protocol (MCP).

How to use GitHub API MCP Server?

To use the GitHub API MCP Server, you need to install the required dependencies, configure the server in your client, and then run the server.

Key features of GitHub API MCP Server?

  • Easy management of GitHub API searches.
  • Utilizes the uv project management tool for dependency management.
  • Configurable server settings for personalized use.

Use cases of GitHub API MCP Server?

  1. Searching for repositories on GitHub efficiently.
  2. Integrating GitHub search capabilities into applications.
  3. Managing multiple GitHub API requests seamlessly.

FAQ from GitHub API MCP Server?

  • What dependencies are required?

You need to install 'uv', 'PyGithub', and 'python-dotenv'.

  • Is there a specific configuration needed?

Yes, you need to configure the server settings in your client as per the provided JSON structure.

  • What programming language is used?

The project is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
HuangZeLinCute
Star
0
Language
Python
License
MIT 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