code-mcp

Created By
jtmckaya year ago
Reusable MCP server setup to augment AI coding agents with specific repo guidelines
Overview

what is code-mcp?

code-mcp is a reusable server setup designed to enhance AI coding agents by providing specific repository guidelines.

how to use code-mcp?

To use code-mcp, set up the server according to the provided guidelines and integrate it with your AI coding agents to ensure they follow the specified repository standards.

key features of code-mcp?

  • Reusable server setup for AI coding agents
  • Customizable repository guidelines
  • Easy integration with existing coding workflows

use cases of code-mcp?

  1. Standardizing coding practices across multiple projects.
  2. Assisting AI agents in adhering to specific coding guidelines.
  3. Streamlining the development process by providing clear repository structures.

FAQ from code-mcp?

  • Can code-mcp be used with any AI coding agent?

Yes! code-mcp is designed to be compatible with various AI coding agents.

  • Is there documentation available for setting up code-mcp?

Yes! Comprehensive documentation is available on the GitHub repository.

  • Is code-mcp free to use?

Yes! code-mcp is open-source and free for everyone.

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

5 hours ago