🔄 MCP + Cursor GitHub Setup

Created By
Ankitkushwaha90a year ago
Overview

What is MCP + Cursor GitHub Setup?

MCP + Cursor GitHub Setup is a project that enables users to control GitHub repositories through the Cursor AI-first code editor by connecting it to a local MCP (Model Context Protocol) server.

How to use MCP + Cursor GitHub Setup?

To use this setup, you need to run your MCP server locally and configure Cursor to connect to it. Follow the step-by-step guide provided in the documentation to set up your environment and connect to GitHub.

Key features of MCP + Cursor GitHub Setup?

  • Full control over GitHub repositories via Cursor commands.
  • Ability to create, update, and delete repositories and files.
  • Integration with GitHub API for seamless operations.
  • Supports automation workflows for repository management.

Use cases of MCP + Cursor GitHub Setup?

  1. Automating CI/CD pipelines using GitHub Actions.
  2. Managing repositories through terminal commands without manual intervention.
  3. Triggering repository events using LLM (Large Language Model) agents.
  4. Securely managing GitHub tokens and repository access.

FAQ from MCP + Cursor GitHub Setup?

  • What do I need to get started?
    You need Node.js, npm, and a GitHub account to set up the MCP server and connect it to Cursor.

  • Is there a way to automate repository management?
    Yes! You can use terminal commands to create, delete, and manage repositories automatically.

  • How do I secure my GitHub tokens?
    It is recommended to keep your tokens in a secure configuration file and use environment variables for production.

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

a day ago
Crevio

2 days ago