metacontract mcp

Name: metacontract mcp
Author: metacontract

@metacontract

代码仓库

关于 metacontract mcp

A Model Context Protocol (MCP) server for metacontract smart contract development.

#smart-contract #evm #metacontract #foundry #mcp

基本信息

分类

其他

传输方式

stdio

发布者

metacontract

提交者

kai hiroi

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "mc-mcp": {
      "command": "mc-mcp",
      "env": {
        "MC_PROJECT_ROOT": "/path/to/your/project"
      }
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is metacontract mcp?

mc-mcp is an extensible MCP server for the metacontract (mc) framework. It enables AI-powered smart contract development workflows via Foundry integration and semantic documentation search, exposing tools for project setup, testing, deployment, and documentation retrieval.

How to use metacontract mcp?

Install via cargo install mc-mcp, add the server to your MCP client (e.g., Cursor, Cline, RooCode) with MC_PROJECT_ROOT set to your project directory. The server automatically starts and provides tools like mc_search_docs_semantic, mc_setup, mc_test, mc_deploy, and mc_upgrade. An optional mcp_config.toml file under the project root customizes reference sources and script paths.

Key features of metacontract mcp

Layered (onion) architecture for maintainability
Rust implementation for performance and safety
Embedded Qdrant vector DB for fast semantic search
Local embedding generation via fastembed-rs
Markdown parsing for documentation indexing
Prebuilt documentation index auto-downloaded from GitHub Releases

Use cases of metacontract mcp

Initialize a new Foundry project with the metacontract template
Perform semantic search over mc, Solidity, and user documentation
Run TDD cycles: write tests and execute mc_test via your agent
Deploy or upgrade contracts using scripts defined in mcp_config.toml
Calculate ERC-7201 namespaced storage slots

FAQ from metacontract mcp

What is `MC_PROJECT_ROOT` and why is it required?

MC_PROJECT_ROOT is an environment variable specifying the project root directory. It is required because path resolution is delegated to the MCP client, ensuring consistent behavior across environments. If unset or non-existent, the server returns an error.

How do I configure reference sources and scripts?

Place a mcp_config.toml file in your MC_PROJECT_ROOT directory. It defines documentation sources (local paths) and default Foundry scripts for deploy/upgrade. If the file is missing, mc-mcp uses built-in defaults.

What MCP transports are supported and how is authentication handled?

mc-mcp uses stdio transport (as shown in client configurations). No authentication mechanism is documented.

Where does the documentation index data live?

On first startup, the prebuilt documentation index (prebuilt_index.jsonl.gz) is downloaded from the latest GitHub Release and cached in the system cache directory. The path can be overridden in mcp_config.toml via prebuilt_index_path.

Are there any known runtime limits or dependencies?

The server requires Rust, Foundry (for test/deploy tools), and an MCP-compatible client. Tests may hit OS file descriptor limits (ulimit -n 4096 recommended) or embedding model cache lock errors—these can be resolved with make clean-cache and single-threaded test execution.