Overview

The Allternit Plugin Adapter layer lets you bring external capability manifests into the platform as first-class plugins. Adapters translate a foreign manifest format into the native Plugin / PluginContext contract so that third-party tools, views, and commands can be discovered and executed by the Allternit runtime without rewriting them. The reference adapter implements the multi-modal capability format used by local-model plugin ecosystems. It validates a manifest, spawns the declared server process, and registers each capability tool into the runtime ToolRegistry.

Base path / usage

Plugin adapters live in the platform plugin runtime:
The adapter is consumed by PluginRegistry.registerQwenMMPlugin() or instantiated directly in SDK / CLI code:

Concepts

Manifest schema

Capability manifest

Marketplace manifest

API / commands

Registering a capability

TypeScript SDK

CLI

Request / response examples

Load a capability manifest

Request:
Response shape (the adapter instance):

Activate and invoke a tool

Request:
Response:

Get server spawn command

Request:
Response:

Validation errors

Lifecycle

Security notes

  • Adapters spawn a child process using the command declared in the manifest. Review the command and arguments before loading an untrusted manifest.
  • Config values are merged into the server environment. Do not commit secrets to manifest files; pass them through config at runtime.
  • Tool input schemas are validated by the runtime before execute() is called, but the adapter itself does not re-validate at invocation time.