GitHub SSH MCP Server - 智能访问检测版

Created By
pyz11a year ago
增强版GitHub MCP Server,支持智能SSH访问检测和自动访问方式切换
Overview

What is GitHub SSH MCP Server?

GitHub SSH MCP Server is an enhanced version of the GitHub MCP (Model Context Protocol) Server designed for Cursor IDE and other MCP-supporting tools. It adds intelligent SSH access detection capabilities, automatically selecting the best access method for GitHub.

How to use GitHub SSH MCP Server?

To use the server, clone the project from GitHub, compile it, and configure it in your Cursor settings with your GitHub Personal Access Token.

Key features of GitHub SSH MCP Server?

  • Intelligent SSH access detection
  • Automatic SSH key detection
  • SSH configuration validation
  • Real-time connection testing
  • Smart access switching between SSH and HTTPS
  • Result caching mechanism for performance optimization

Use cases of GitHub SSH MCP Server?

  1. Automatically detect and switch GitHub access methods based on availability.
  2. Manage GitHub repositories, issues, and pull requests efficiently.
  3. Test and validate SSH connections for secure access.

FAQ from GitHub SSH MCP Server?

  • What SSH keys are supported?

RSA, Ed25519, ECDSA, and DSA keys are supported.

  • Is a GitHub Personal Access Token required?

Yes, it is necessary for authentication and access to GitHub APIs.

  • How does the caching mechanism work?

The results of access detection are cached for 5 minutes to improve performance.

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