Skip to main content
Public ASGI application factory for a user-owned tai server process. create_app is the programmatic entry point for embedding the tai MCP application inside a host-owned ASGI process — a plain uvicorn main:app run or a mount inside an existing FastAPI/Starlette host:
The returned Starlette app carries the full worker lifespan (manifest load, app_context, transport selection, and the inner FastMCP lifespan), so the host serves it exactly as the runtime CLI serves its own workers. One app per process. The tai42_app contract handle and the built app are process-global singletons, so a second create_app lifespan entered while one is already active raises loudly rather than silently rebinding the handle; sequential lifespans in one process (enter -> exit -> enter) stay legal. Deliberately CLI-owned and absent here: root-logger configuration (an embedded app never touches the host’s logging), the Prometheus multiprocess metrics environment (an embedded process serves the in-process registry), and process-fleet orchestration. Fleet config-reload fan-out is the app’s internal worker bus: an embedded worker joins it like any other process when TAI_BUS_REDIS_URL is set (the rules cannot count sibling processes in an embedded host, so set it in any multi-process embed).

​
Transport

tai42_skeleton.asgi.Transport

​
create_app

tai42_skeleton.asgi.create_app
Build the public ASGI app for a user-owned process. One app per process: the returned app’s lifespan claims a process-global one-app token, and a second lifespan entered while one is active raises. The transport and stateless_http arguments are validated at call time. Parameters Returns — A Starlette app whose lifespan claims the one-app token, stamps the manifest env, builds the app singleton, enters app_context and the inner FastMCP lifespan, and releases the token (restoring the env) on exit.

​
lifespan

tai42_skeleton.asgi.lifespan
Return a create_app app’s lifespan context manager, for composing into a host lifespan when the app is mounted. Mounting the factory app is not enough on its own: Starlette does not run a mounted sub-app’s lifespan, so the host must run it. Enter the returned context manager inside the host’s own lifespan so the tai app’s worker startup (manifest load, app_context, transport selection, the inner FastMCP lifespan) runs for the host process’s lifetime. Parameters Returns — The app’s lifespan context manager (app.router.lifespan_context(app)), to be entered inside the host lifespan.