Package reference
Invokta publishes three runtime packages and six supporting packages. Each has one bounded responsibility.
Runtime packages
Section titled “Runtime packages”| Package | Public role | Start here |
|---|---|---|
@invokta/core |
Capability contracts, execution, composition, errors, and events | Core reference |
@invokta/cli |
Local list, describe, and run over engine.invoke |
CLI reference |
@invokta/mcp |
MCP tools over stdio and stateless Streamable HTTP | MCP reference |
The core has no adapter or SDK dependency. CLI and MCP import only its public API and never call capability handlers directly.
Supporting packages
Section titled “Supporting packages”| Package | Public role | Start here |
|---|---|---|
@invokta/tooling |
Validate a built, tracked capability composition in development or CI | Tooling reference |
@invokta/devtools |
Open the MCP and CLI workbenches, or serve a built engine with a web inspector, trace, and doctor diagnostics | Devtools reference |
@invokta/installer |
Install and manage Action Engine MCP servers in supported local clients | Installer reference |
@invokta/deploy |
Scaffold/package HTTP deployment artifacts, probe health, and inspect OAuth discovery | Deploy reference |
create-invokta-engine |
Create a standalone starter engine and install its dependencies | Creator reference |
create-invokta-capability |
Create a standalone atomic capability package | Atomic creator reference |
create-invokta-capability-library |
Create a standalone capability-library package | Library creator reference |
Supporting packages do not create another capability execution path. The creators write projects, tooling imports a trusted composition module, the installer updates client configuration without invoking an engine, and deploy generates files or makes one probe request.
Shared requirements
Section titled “Shared requirements”- Native ESM
- Node.js 22.20.0 or later
- Package-root imports only unless a package explicitly documents a subpath
- Runtime behavior remains on
engine.invoke
Use the error reference for capability invocation errors. Creator, tooling, installer, and deploy diagnostics have separate application-specific contracts.