Skip to main content

Introduction to io.Intelligence Framework

io.Intelligence helps teams make their io.Connect applications AI-ready. Instead of rebuilding existing systems, you can add AI assistants, business context awareness, and standardized tool access on top of the applications and workflows you already have.

The framework is designed as a package ecosystem. Some packages help you expose application capabilities to AI systems. Others help you build assistant experiences in the browser or adopt a ready-made assistant offering for your application.

What io.Intelligence Enables​

With io.Intelligence, you can:

  • connect AI assistants to your application ecosystem through Model Context Protocol (MCP)
  • capture and share business context so assistants can respond more intelligently
  • build custom web assistant experiences on top of io.Connect
  • add a ready-made assistant UI to an existing application, starting with Angular
  • bridge a Mastra backend to the io.Intelligence Agent Protocol used by frontend clients

The Package Ecosystem​

The current documentation covers five module areas that often get combined in real deployments.

MCP​

The MCP packages provide the infrastructure layer for exposing tools, resources, and prompts to AI assistants. They cover core abstractions and the main transport options used across the framework.

Best fit for:

  • teams exposing application capabilities to AI assistants
  • developers building MCP servers and transports
  • platform teams standardizing AI integration patterns

Learn more: MCP Overview

Working Context​

Working Context collects and maintains the business context users are actively working with, such as selections, entities, or workflow state. That context can then be shared with AI assistants and applications.

Best fit for:

  • applications that need context-aware behavior
  • assistants that should understand what the user is working on
  • teams defining a shared context model across apps

Learn more: Working Context Overview

AI Web​

AI Web is the framework-agnostic web SDK for building assistant and copilot experiences on io.Connect. It connects frontend experiences to agent servers, MCP servers, Working Context, and MCP Apps.

Best fit for:

  • teams building a custom assistant UI in the browser
  • developers who want direct control over assistant behavior and integration
  • products that need threads, tools, prompts, and resources in one web SDK

Learn more: AI Web Overview

io.Assist​

io.Assist is the ready-made assistant UI offering in io.Intelligence. It is the module area for framework-specific assistant implementations that let teams embed a packaged assistant experience instead of building the full frontend from scratch.

The first released item in this area is io.Assist NG, the Angular implementation. It is built on top of AI Web and is designed for teams that want to ship an assistant experience quickly inside an Angular application.

Best fit for:

  • teams looking for a packaged assistant experience rather than a custom frontend
  • Angular teams embedding an assistant into an existing app
  • projects that prefer configuration over building a custom chat UI
  • products that want assistant UX, prompt handling, and MCP app support out of the box
  • teams planning around an offering that can expand into additional framework flavors over time

Learn more: io.Assist

AI Server​

AI Server is the server-side module area in io.Intelligence. It covers backend integrations that supply the route and streaming contract used by frontend assistant clients.

The first released item in this area is AI Mastra Bridge, which connects Mastra agents to the io.Intelligence Agent Protocol used by frontend clients and provides the route layer needed for agent discovery, streaming runs, and thread management.

Best fit for:

  • backend teams evaluating the server-side assistant layer
  • projects pairing a backend runtime with AI Web or io.Assist implementations such as io.Assist NG
  • teams using Mastra and looking for the currently released server-side integration

Learn more: AI Server Overview

Choosing the Right Starting Point​

Start with the package that matches your role:

  • building infrastructure for assistant access to apps and tools: start with MCP
  • adding business context to assistants or apps: start with Working Context
  • building a custom web assistant experience: start with AI Web
  • embedding a ready-made assistant experience: start with io.Assist
  • evaluating the backend side of the assistant stack: start with AI Server

Common Package Paths​

Many integrations use more than one package:

Getting Started​

Prerequisites

The exact prerequisites depend on the package you use, but common requirements include:

  • an active io.Intelligence license
  • an io.Connect Desktop or io.Connect Browser environment
  • registered applications in your io.Connect ecosystem
  • a backend that implements the io.Intelligence Agent Protocol for frontend assistant experiences

Next Steps​

If you are evaluating the framework, start with the modules section:

If you are ready to integrate, move into the API reference: