Skip to content

docs(examples): the agui-events service needs the [api] extra #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ciaransweet merged 1 commit into from
Aug 13, 2026
+9 −2
Merged

docs(examples): the agui-events service needs the [api] extra #77

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions examples/agui-events/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ cd examples/agui-events

# terminal 1 — the service: four MCP servers, an agent, the API on :8765
PROVIDER_MODEL=mistral-small-latest PROVIDER_API_KEY=… \
uv run --with langchain-mistralai python -m service
uv run --extra api --with langchain-mistralai python -m service

# terminal 2 — the client
cd web && npm install && npm run dev
Expand All @@ -32,8 +32,15 @@ uses — so the `--with` above is how this example gets one. Any other provider
works the same way with its own package: `openai:gpt-4o-mini` with
`langchain-openai`, and so on.

`--extra api` is not optional. `mcp_agent_api` ships in the base wheel, so it
imports far enough to look installed, but the AG-UI event vocabulary it is
built on lives in that extra — without it the service dies on `No module named
'ag_ui'`. A checkout developed with `uv sync --all-extras` already has it and
will not show this; a clean one, where `uv run` builds the environment from
this command alone, will.

`service/` is laid out the way a deployment of this runtime is, because that is
the more useful thing for it to be. `create_app` supplies the agent's four
the more useful thing for it to be. `create_app` supplies the agent's five
routes, its lifespan and CORS; the service supplies the `build` factory it
awaits, and adds the health probes an orchestrator wants. Connecting to the MCP
servers happens *inside* that factory, so the routes really do answer 503 until
Expand Down