How enactprotocol/enact works
Project type and purpose
• Enact CLI is a monorepo providing:
• A command-line interface (CLI) for packaging, signing, discovering, and executing AI tools
• A minimal MCP (Model Context Protocol) server exposing tool execution over HTTP + a built-in web UI for environment management
• A shared library that implements core logic, security, and pluggable execution providers
File structure
• Top-level:
• packages/cli – CLI commands and entry point (src/index.ts)
• packages/mcp-server – HTTP server & MCP handlers (src/mcp/server.ts)
• packages/shared – Core services, API clients, exec providers, security, web-static assets
• Support files:
• docs/ – design & usage docs
• examples/ – sample tool YAMLs
• scripts/ – build, deploy, test helpers
• Config: Bun (bunfig.toml), TypeScript (tsconfig.json), npm (package.json)
Extract architecture details from README
• Execution providers:
• Dagger (containerized) – default for running external tools
• Direct (host) – for fast CLI operations
• Security: cryptographic signing + verification before execution
• MCP server: exposes 7 core tools via MCP protocol + serves static web UI at port 5555
• External dependencies:
• Enact Registry HTTP API
• Dagger engine (container runtime)
• File system (for local tools, cache, .env)