CodeContextMCP

Created By
offekaa year ago
An MCP server for adding additional repos context using the MCP protocol
Overview

what is CodeContextMCP?

CodeContextMCP is an MCP server designed to enhance the context of additional repositories using the MCP protocol.

how to use CodeContextMCP?

To use CodeContextMCP, set up the server and configure it to connect with your repositories, allowing it to provide contextual information based on the MCP protocol.

key features of CodeContextMCP?

  • Integration with multiple repositories for enhanced context
  • Utilization of the MCP protocol for seamless communication
  • Customizable server settings for specific repository needs

use cases of CodeContextMCP?

  1. Providing contextual information for code reviews across multiple repositories.
  2. Enhancing developer productivity by offering relevant context during coding sessions.
  3. Facilitating better collaboration among teams working on interconnected projects.

FAQ from CodeContextMCP?

  • What is the MCP protocol?

The MCP protocol is a method for servers to communicate and share context about repositories effectively.

  • Is CodeContextMCP free to use?

Yes! CodeContextMCP is open-source and free for everyone to use.

  • How can I contribute to CodeContextMCP?

You can contribute by submitting issues or pull requests on the GitHub repository.

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

Recommend Servers

View All
Hellogrowthcrm

2 hours 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
Payai X402 Tools

11 hours ago