@voidbase-cloud/plugin-ai

The ai plugin of voidbase, as a package of its own. It answers questions about the instance's own data: a chat endpoint, conversations kept as records, and the instance's MCP tools as the means of actually reading and writing rows.

It ships with voidbase and is on by default — @voidbase-cloud/voidbase depends on this package and loads it — so an instance needs nothing here. Install it yourself only to load it into an app that builds its own plugin graph.

What it needs

A model binding. VOIDBASE_AI=1 (or a model name) and the Worker's AI binding is the shipped path; without them the plugin loads and stays idle, and /api/plugins says so.

Why it depends on two sibling packages

The tools it calls are the MCP tools, which are written from the OpenAPI document: it reads documentFor, toolsOf and runTool from @voidbase-cloud/plugin-mcp, and the OpenApiSource type from @voidbase-cloud/plugin-openapi. It names both packages directly rather than the core's re-exports of them, because those packages are what it uses — and the release publishes them, in order, before this one.

Swapping it

An instance loads whichever plugin claims the name ai: install one from a marketplace and it shadows this one, or turn this one off in voidbase.lock. The conversations it keeps are ordinary records, so they survive the swap.

MIT