GitHub MCP Server for Cursor IDE

Created By
alfie-teka year ago
GitHub MCP server for Cursor IDE
Overview

what is GitHub MCP Server for Cursor IDE?

GitHub MCP Server for Cursor IDE is a powerful integration server that allows users to manage their GitHub repositories directly from the Cursor IDE environment, providing a seamless development experience.

how to use GitHub MCP Server?

To use the GitHub MCP Server, clone the repository, install the dependencies, configure your environment variables, and start the server. You can then interact with the server using various API endpoints.

key features of GitHub MCP Server?

  • Create and manage GitHub repositories directly from Cursor IDE.
  • Secure token-based authentication for API access.
  • Comprehensive error handling and logging.
  • Rate limiting protection to prevent abuse.
  • Webhook support (coming soon).

use cases of GitHub MCP Server?

  1. Automating repository creation and management tasks.
  2. Integrating GitHub functionalities into the Cursor IDE workflow.
  3. Enhancing collaboration by managing repositories from a single interface.

FAQ from GitHub MCP Server?

  • What are the prerequisites for using the GitHub MCP Server?

You need Node.js, npm, a GitHub account with a Personal Access Token, and Cursor IDE.

  • How do I create a new repository using the server?

You can create a new repository by sending a POST request to the /api/github/repos endpoint with the required parameters.

  • Is there support for error handling?

Yes, the server includes comprehensive error handling for various scenarios, including invalid tokens and rate limiting.

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