MCP ConfigsMay 14, 2026·2 min read

EDDI — One-Command Agent Orchestration (MCP)

Boot EDDI via its one-command installer to run agents with Docker Compose and connect tools via MCP/A2A; includes an `eddi` CLI for updates.

Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Native · 94/100Policy: allow
Agent surface
Any MCP/CLI agent
Kind
Mcp
Install
Docker|Curl
Trust
Trust: Established
Entrypoint
curl -fsSL https://raw.githubusercontent.com/labsai/EDDI/main/install.sh | bash
Universal CLI install command
npx tokrepo install 0d125fb1-2659-5656-8652-0fb7929940b8
Intro

Use EDDI when you want a Docker-based agent runtime you can bring up quickly and integrate with MCP-compatible clients.

Boot EDDI via its one-command installer to run agents with Docker Compose and connect tools via MCP/A2A; includes an eddi CLI for updates.

Best for: teams prototyping agent runtimes with Docker Compose and a standardized tool surface (MCP/A2A) before production hardening

Works with: Docker, curl installer, optional Maven build for contributors, MCP-capable clients

Setup time: ~10–25 minutes (installer + compose pull/start)

Key facts (verified)

  • GitHub: 351 stars · 113 forks · pushed 2026-05-13.
  • License: Apache-2.0 · owner avatar + repo URL verified via GitHub API.
  • Entrypoint (README-backed): curl -fsSL https://raw.githubusercontent.com/labsai/EDDI/main/install.sh | bash.

Main

  • Start with a minimal tool surface and expand only after you have observability and reset/recovery procedures.
  • Store secrets in the mechanism the installer sets up; avoid baking keys into compose files or images.
  • Pin versions for reproducible environments once you move from demo to team usage.

README excerpt (source)

![EDDI Banner Image](/screenshots/EDDI-Readme-banner-image.webp)

# E.D.D.I — Multi-Agent Orchestration Middleware for Conversational AI

[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/12355/badge?v=2)](https://www.bestpractices.dev/projects/12355) [![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/labsai/EDDI/badge)](https://securityscorecards.dev/viewer/?uri=github.com/labsai/EDDI) [![Codacy Badge](https://app.codacy.com/project/badge/Grade/2c5d183d4bd24dbaa77427cfbf5d4074)](https://app.codacy.com/organizations/gh/labsai/dashboard?utm_source=github.com&utm_medium=referral&utm_content=labsai/EDDI&utm_campaign=Badge_Grade)

[![CI](https://github.com/labsai/EDDI/actions/workflows/ci.yml/badge.svg)](https://github.com/labsai/EDDI/actions/workflows/ci.yml) [![CodeQL](https://github.com/labsai/EDDI/actions/workflows/codeql.yml/badge.svg)](https://github.com/labsai/EDDI/actions/workflows/codeql.yml) ![Tests](https://img.shields.io/badge/tests-5%2C100%2B-brightgreen) ![Coverage](https://img.shields.io/badge/coverage-%3E80%25-brightgreen)

FAQ

Q: Does it require Docker? A: The README quick start requires Docker and uses Docker Compose via the installer.

Q: How do updates work? A: The installer creates an eddi CLI wrapper; eddi update pulls and restarts containers.

Q: Safe first use case? A: Start with non-sensitive test data and a read-only tool setup before connecting real systems.

🙏

Source & Thanks

Source: https://github.com/labsai/EDDI > License: Apache-2.0 > GitHub: 351 stars · 113 forks · pushed 2026-05-13

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets