Flash-GitHub

Created By
ruilacerdaa year ago
A GitHub API integration server using the MCP (Message Control Protocol) framework
Overview

what is Flash-GitHub?

Flash-GitHub is a GitHub API integration server that utilizes the MCP (Message Control Protocol) framework to provide a standardized interface for interacting with GitHub repositories.

how to use Flash-GitHub?

To use Flash-GitHub, install the required dependencies using pip install -r requirements.txt, configure your GitHub API token in a .env file, and run the server with python flash-github.py.

key features of Flash-GitHub?

  • Search GitHub repositories
  • Create new repositories
  • Retrieve file content from repositories
  • List contents of repositories
  • Get detailed repository information
  • Pull changes from repositories to local directories
  • Push local changes to repositories
  • Compare local directories with GitHub repositories

use cases of Flash-GitHub?

  1. Automating repository management tasks.
  2. Integrating GitHub functionalities into other applications.
  3. Facilitating collaboration on GitHub projects.

FAQ from Flash-GitHub?

  • What is the MCP framework?

The MCP framework is a protocol that standardizes communication between different services, making it easier to integrate with APIs like GitHub.

  • Is Flash-GitHub free to use?

Yes! Flash-GitHub is open-source and free to use under the MIT License.

  • How do I get my GitHub API token?

You can generate a GitHub API token from your GitHub account settings under Developer settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ruilacerda
Star
0
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)

20 hours ago
Gpt Scrambler

2 days ago