Skip to main content
By the end you will have the platform running on your machine: an API on port 8000, a dashboard on port 3000, and the supporting services — Postgres, Valkey, Temporal, the Go MCP manager, object storage and Ory Kratos — running alongside them.
This is the development stack, tuned for hot reload and throwaway credentials. For a real deployment, start at requirements.

Before you start

Start the stack

1

Clone the repository

2

Create the environment file

The defaults are development credentials and work as they are. Do not reuse this file anywhere real — see configuration for what each value does.
3

Start the services

Despite its help text, make up-dev runs docker compose up in the foreground, without -d. It holds the terminal. Open a second terminal for the next steps, or run docker compose -f docker-compose.dev.yaml up -d yourself.
First run pulls and builds images, which takes several minutes. The stack is ready when the API answers.
4

Check the API

The MCP manager has its own health endpoint:
Interactive API documentation is at http://localhost:8000/docs.
5

Start the dashboard

The dev stack does not include the frontend — it is commented out in docker-compose.dev.yaml so you can run it with hot reload. In a second terminal:
Open http://localhost:3000. Ory Kratos redirects login and consent to this exact origin, so use localhost:3000 rather than 127.0.0.1.

What you have

The services you will actually interact with: The dev stack additionally runs Keto, OpenFGA and Hydra, which the production Compose file does not.

Stop the stack

make down-clean also drops the volumes, so the next start is from scratch.

How it works

The request path across control and data plane. Read this before anything else.

Create and configure an agent

Give an agent a model and run its first task.

Troubleshooting

When a service will not come up.

Self-host requirements

Running it somewhere other than your laptop.
Last modified on September 17, 2026