github-mcp

Created By
kao73a year ago
MCP server for GitHub
Overview

what is github-mcp?

github-mcp is a server designed to facilitate the MCP (Multi-Channel Publishing) for GitHub, allowing users to manage and publish content across multiple channels seamlessly.

how to use github-mcp?

To use github-mcp, clone the repository from GitHub, configure the server settings according to your needs, and run the server to start managing your content.

key features of github-mcp?

  • Multi-channel content publishing capabilities
  • Easy integration with GitHub repositories
  • Customizable server settings for different publishing needs

use cases of github-mcp?

  1. Publishing documentation across various platforms from a single GitHub repository.
  2. Managing content updates for multiple projects simultaneously.
  3. Streamlining the workflow for teams working on collaborative projects.

FAQ from github-mcp?

  • What is MCP?

MCP stands for Multi-Channel Publishing, which allows content to be published across various platforms from a single source.

  • Is github-mcp free to use?

Yes! github-mcp is open-source and free to use under the Apache-2.0 license.

  • How do I contribute to github-mcp?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kao73
Star
0
Language
-
License
Apache-2.0 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