ZooGent

Lightweight AI agent orchestrator with built-in Architect AI. Multi-team support - run isolated agent teams in a single instance. Describe what you want to automate, get working agents.

Quick Start

npx zoogent create my-agents
cd my-agents
npx zoogent start

Open http://localhost:3200. Create account > create team > add Anthropic API key in Team Settings > go to Architect and describe what you want to automate.

What is ZooGent

ZooGent is a process manager for AI agent teams. It spawns agents, routes tasks between them, tracks costs, and captures logs. Each agent is a standalone script that calls its own LLM.

Multi-team isolation - one instance, multiple teams. Each team has its own agents, skills, memory, knowledge, Architect chat, and API keys. Teams don't see each other's data.

Two ways to use it:

1. Chat UI - open the Architect page in your browser, describe your task in plain language. The Architect AI designs the team, creates skills, writes agent code, and tests everything.

2. Claude Code + MCP - connect MCP to Claude Code, build agents from the terminal with full control over code and configuration.

Both paths use the same API, same database, same agents. Pick whichever fits your workflow.

Getting Started

Path 1: Web UI + Architect

Local

npx zoogent create my-agents
cd my-agents
npx zoogent start

1. Open http://localhost:3200
2. Create your account
3. Create a team
4. Go to Team Settings > add your Anthropic API key
5. Go to Architect > describe what you want to automate

Architect designs agents, writes skills, generates code, and tests everything through conversation.

Server

npx zoogent create my-agents
cd my-agents
npx zoogent start -d

Set BETTER_AUTH_URL to your public URL in .env. Use a reverse proxy (nginx, Caddy) or deploy via Docker (see Deployment section). The web UI is the same - just accessed remotely.

Path 2: Claude Code + MCP

Local

Start the server locally, then connect Claude Code via MCP:

npx zoogent create my-agents
cd my-agents
npx zoogent start -d

Add the MCP server to Claude Code. Run this from inside the project you want to work in — each project typically binds to its own ZooGent instance (its own SQLite, teams, agents, API keys), so the MCP config should live with the project:

claude mcp add zoogent -s project -- npx zoogent mcp

-s project writes the config to .mcp.json in the project root — commit it and teammates who clone the repo get the same MCP setup automatically.

Claude Code auto-discovers the local server. Ask Claude to create a team and design your agents.

Remote server

Deploy ZooGent to a server (see Deployment). Open the web UI, create an account, go to Settings > generate an API key.

Run from inside the project that should connect to this ZooGent instance:

claude mcp add zoogent -s project \
  -e ZOOGENT_URL=https://your-domain.com \
  -e ZOOGENT_API_KEY=zg_your-key-from-settings \
  -- npx zoogent mcp

Each project can point at its own ZooGent (local or remote), with its own URL and API key. Keeping the config in the project's .mcp.json makes that mapping explicit. Use -s user instead only if you have a single shared ZooGent instance across all projects.

{
  "mcpServers": {
    "zoogent": {
      "command": "npx",
      "args": ["zoogent", "mcp"],
      "env": {
        "ZOOGENT_URL": "https://your-domain.com",
        "ZOOGENT_API_KEY": "zg_your-key-from-settings"
      }
    }
  }
}

Claude Code connects to the remote server. Create teams, design agents, write code - all through MCP tools. Agents run on the server.

How It Works

1. Create a team for your business process
2. Describe what you want automated in the team's Architect c

... View full README on GitHub