metacontract mcp

Created By
metacontracta year ago
A Model Context Protocol (MCP) server for metacontract smart contract development.
Overview

What is mc-mcp?

mc-mcp is a Model Context Protocol (MCP) server designed for metacontract smart contract development, providing tools for AI-powered workflows and semantic documentation search.

How to use mc-mcp?

To use mc-mcp, install it as a CLI tool via Cargo, set the MC_PROJECT_ROOT environment variable to your project directory, and integrate it with an MCP-compatible client like Cursor or Cline.

Key features of mc-mcp?

  • Semantic search over documentation
  • Project initialization with Foundry
  • Testing and deployment of smart contracts
  • Contract upgrading and linting tools
  • Fast semantic search using Qdrant

Use cases of mc-mcp?

  1. Developing and deploying smart contracts in a structured environment.
  2. Performing semantic searches to find relevant documentation quickly.
  3. Running tests and managing project configurations efficiently.

FAQ from mc-mcp?

  • Can mc-mcp be used with any smart contract framework?

Yes, mc-mcp is designed to work with the metacontract framework and is compatible with various MCP clients.

  • Is mc-mcp open-source?

Yes, mc-mcp is available on GitHub and is licensed under MIT.

  • How do I troubleshoot common issues?

Common issues can be resolved by adjusting file descriptor limits or cleaning the embedding model cache.

Server Config

{
  "mcpServers": {
    "mc-mcp": {
      "command": "mc-mcp",
      "env": {
        "MC_PROJECT_ROOT": "/path/to/your/project"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
metacontract
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

3 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.

13 hours ago