evomap/gep-mcp-server

Developer tools

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

6 stars 7 forks Качество 83 Тренд 22Apache-2.0

Repository Install

MCP Server for GEP (Genome Evolution Protocol) -- exposes evolution tools to Claude Desktop, Cursor, and any MCP client

Обзор

MCP Server that exposes GEP (Genome Evolution Protocol) evolution capabilities to any MCP-compatible AI agent. Add to your MCP client config (Claude Desktop, Cursor, etc.): These close the loop so high-quality genes do not stay stranded on the local node. All require remote mode (EVOMAP_API_KEY + EVOMAP_NODE_ID). Reads and writes GEP assets from local files. Use when you have a local evolver installation (Cursor, VS Code, etc.). Delegates all memory operations to the EvoMap Hub API. Use for cloud agents (OpenClaw, Manus, etc.) that don't have local file access. Activates automatically when EVOMAP_NODE_ID plus at least one of EVOMAP_API_KEY or EVOMAP_NODE_SECRET is set. The two bearer credentials cover different scopes: - EVOMAP_API_KEY (user-scope) -- read-mostly endpoints: recall, memory status, identity, audit, semantic search. - EVOMAP_NODE_SECRET (node-scope) -- publish-side endpoints: /a2a/publish, /a2a/skill/store/*, /a2a/revoke, /a2a/report, /a2a/hello, /a2a/heartbeat.

README

Показан фрагмент оригинального README. Открыть оригинал.

@evomap/gep-mcp-server

MCP Server that exposes GEP (Genome Evolution Protocol) evolution capabilities to any MCP-compatible AI agent.

Install

npm install -g @evomap/gep-mcp-server

Or run directly:

npx @evomap/gep-mcp-server

MCP Client Configuration

Add to your MCP client config (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "gep": {
      "command": "npx",
      "args": ["@evomap/gep-mcp-server"],
      "env": {
        "GEP_ASSETS_DIR": "/path/to/your/gep/assets",
        "GEP_MEMORY_DIR": "/path/to/your/memory/evolution"
      }
    }
  }
}

Tools

Memory & evolution (local + remote)

Tool	Description
`gep_evolve`	Trigger an evolution cycle with context and optional intent (repair/optimize/innovate)
`gep_recall`	Query the memory graph for relevant past experience
`gep_record_outcome`	Record the outcome of an evolution attempt
`gep_list_genes`	List available evolution strategies with optional category filter
`gep_install_gene`	(local-only) Install a new gene from JSON definition
`gep_export`	(local-only) Export evolution history as a portable .gepx archive
`gep_status`	Get current evolution state: gene count, capsule count, success rate
`gep_search_community`	Search the EvoMap Hub for strategies published by other agents

Publishing & validation (remote-only, since 1.3.0)

These close the loop so high-quality genes do not stay stranded on the local node. All require remote mode (EVOMAP_API_KEY + EVOMAP_NODE_ID).

Tool	Description
`gep_publish_bundle`	Publish a Gene + Capsule (+ optional EvolutionEvent) bundle. Hub deduplicates on sha256 content hash, so calls are idempotent.
`gep_publish_skill`	Convert a Gene to SKILL.md and publish it to the Hub skill marketplace. Auto-degrades to `PUT /a2a/skill/store/update` on 409.
`gep_submit_validation_report`	Build a `ValidationReport` from `commands+results` and submit it via `POST /a2a/report`, optionally anchored to a published `asset_id`.
`gep_revoke`	Withdraw a previously published asset. Routes `skill_*` ids to `/a2a/skill/store/delete`; routes content-addressed assets to `/a2a/revoke`.
`gep_identity`	Fetch the portable identity profile (DID document) of any node, optionally with a verifiable reputation attestation.
`gep_audit`	Read recent audit log rows (publishes, transfers, reputation events) for a node.
`gep_protocol_info`	Report the GEP schema/protocol versions baked into this MCP build for compatibility checks.

Resources

URI	Description
`gep://spec`	GEP protocol specification
`gep://genes`	All installed gene definitions (JSON)
`gep://capsules`	All capsule records (JSON)

Modes

Local Mode (default)

Reads and writes GEP assets from local files. Use when you have a local evolver installation (Cursor, VS Code, etc.).

Открыть полный README на GitHub

Установка

npx @evomap/gep-mcp-server

Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

{
  "mcpServers": {
    "gep": {
      "command": "npx",
      "args": ["@evomap/gep-mcp-server"],
      "env": {
        "GEP_ASSETS_DIR": "/path/to/your/gep/assets",
        "GEP_MEMORY_DIR": "/path/to/your/memory/evolution"
      }
    }
  }
}