Gitingest-MCP

Created By
puravparaba year ago
mcp server for gitingest
Overview

What is Gitingest-MCP?

Gitingest-MCP is an MCP server designed for Gitingest, enabling clients like Claude Desktop to extract information from GitHub repositories efficiently.

How to use Gitingest-MCP?

To use Gitingest-MCP, you can install it via Smithery or manually clone the repository and configure it with your MCP client.

Key features of Gitingest-MCP?

  • Quickly extracts repository summaries, project directory structures, and file content from GitHub.
  • Supports integration with various MCP clients like Claude Desktop, Cline, and Cursor.

Use cases of Gitingest-MCP?

  1. Extracting summaries of GitHub repositories for quick insights.
  2. Navigating project directory structures for better understanding of repository layouts.
  3. Accessing file content directly through MCP clients for efficient development workflows.

FAQ from Gitingest-MCP?

  • How do I install Gitingest-MCP?

You can install it via Smithery or manually by cloning the repository and following the setup instructions.

  • What clients are compatible with Gitingest-MCP?

Gitingest-MCP works with MCP clients like Claude Desktop, Cline, and Cursor.

  • Is there documentation available for troubleshooting?

Yes, you can refer to the MCP server documentation for help.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
puravparab
Star
5
Language
Python
License
MIT license

Recommend Servers

View All
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.

8 hours ago