Skip to main content
The MCP server is the Middleware API offered over the Model Context Protocol. Compatible agents and clients call the same workspace, ingestion, query, and knowledge tools without a custom integration. The endpoint is api.aiql.io/mcp. Developer setup lives at docs.aiql.io/mcp/overview. Authentication is an API key, or OAuth for interactive clients. The same key works on the HTTP API and on MCP. OAuth binds the session to a workspace. An API key is scoped to a workspace per request.

Pipeline

The same four steps as convert, split, shape, and extract on the Middleware API. An agent can chain them, or run them as one ingestion.

Workspaces

Ingestions

A managed job that runs the four pipeline steps and loads the result into the session workspace.

Queries

Natural-language questions over already ingested workspace data. The same answer models as Explore in Observatory. Modes are ask, reason, and build.

Sources and knowledge

Inspection of ingested sources and the structured records extracted from them. Retrieval fuses exact, lexical, and semantic match. See Embeddings.

Artifacts

Work products on top of workspace knowledge. The same kinds of output as the Artifacts API.

Terminology

Clinical coding against the Terminology API.

Preferences, rules, and knowledge

Workspace memory that later queries follow. The same kinds of record as Studio setup.