Overview
AI Server is the server-side module offering in io.Intelligence. It covers the backend layer that frontend assistant clients rely on for agent runs, streaming, threads, and the io.Intelligence Agent Protocol.
Today, the first released item in this offering is AI Mastra Bridge.
Backend Offering
AI Server is where the backend side of an io.Intelligence assistant integration comes together.
If AI Web and io.Assist NG represent the frontend side of the assistant experience, AI Server represents the server-side module area that supplies the backend contract those clients need.
Why Teams Start with AI Server
Understand the backend layer
See where server-side integrations fit in the overall io.Intelligence architecture.
Find the current released item
Start with AI Mastra Bridge when your backend runtime is Mastra and your frontend expects the io.Intelligence Agent Protocol.
Connect frontend and runtime cleanly
Use the server-side module area to supply runs, threads, agents, and streaming behavior to frontend assistant clients.
Keep the stack organized
Separate the frontend assistant modules from the backend integrations that support them.
What AI Server Covers
AI Server is the module area for server-side integrations that sit between agent runtimes and frontend clients that speak the io.Intelligence Agent Protocol.
At the moment, this area includes:
| Released item | Purpose |
|---|---|
| AI Mastra Bridge | Connects Mastra agents to frontend clients through a stable HTTP route layer that implements the io.Intelligence Agent Protocol |
Who It Helps
| Audience | Why it matters |
|---|---|
| Backend teams | Find the server-side integration surface for assistant products built on io.Intelligence |
| Frontend teams | Understand where the backend contract comes from and which server-side module to pair with their client |
| Platform teams | Keep frontend and backend assistant responsibilities organized within the broader module ecosystem |
| Product owners | Navigate the backend part of the offering without jumping directly into API reference pages |
When to Start Here
Start with AI Server when you are:
- evaluating the backend side of the io.Intelligence assistant stack
- looking for the module area that serves AI Web or io.Assist NG
- using Mastra and want the currently released backend integration
- mapping the overall architecture before choosing a specific server-side package
If you already know your backend runtime is Mastra, continue directly to AI Mastra Bridge.
How It Fits in the Stack
Step 1 Frontend modules such as AI Web or io.Assist NG need a backend contract for runs, agents, and threads.
Step 2 AI Server represents the module area that provides those server-side integrations.
Step 3 The first released item in that area is AI Mastra Bridge, which connects Mastra to frontend clients through the io.Intelligence Agent Protocol.
Step 4 MCP and Working Context can then complement that assistant stack when tools, resources, prompts, or live business context are needed.
Next Steps
- AI Mastra Bridge for the first released AI Server item
- Agent Protocol Reference for the shared frontend-backend contract
- AI Mastra Bridge Capabilities for the deeper bridge behavior
- AI Mastra Bridge API Overview for the public backend reference