Cursor MCP Server

Created By
mayur29a year ago
Repository created using MCP GitHub server
Overview

what is Cursor MCP Server?

Cursor MCP Server is a GitHub server integration for Cursor IDE using the Multi-Cloud Protocol (MCP), enabling seamless interaction with GitHub repositories directly from the IDE.

how to use Cursor MCP Server?

To use Cursor MCP Server, install Cursor IDE, configure your GitHub credentials in the MCP configuration file, and set up your Personal Access Token (PAT) with the necessary permissions.

key features of Cursor MCP Server?

  • GitHub API integration for enhanced functionality
  • Repository management capabilities
  • Issue tracking and pull request handling
  • File operations and code search capabilities

use cases of Cursor MCP Server?

  1. Managing GitHub repositories directly from Cursor IDE.
  2. Tracking issues and handling pull requests seamlessly.
  3. Performing code searches across multiple GitHub repositories.

FAQ from Cursor MCP Server?

  • What is required to use Cursor MCP Server?

You need to have Cursor IDE installed and configure your GitHub credentials.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit a Pull Request.

  • What license is the project under?

The project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mayur29
Star
0
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago