Skip to main content
This page is for developers and power users who want to drive Enconvo from Terminal, a script or another app. The enconvo command ships with the Enconvo desktop app, with no separate install, and the app serves every installed plugin’s routes over a local HTTP API. Keep Enconvo running for commands that use its local runtime.

Find commands

Append -h to the command you are investigating to see its current subcommands and options. Open Settings → CLI Guide to see the installed extensions that expose CLI commands. Click a name to copy its enconvo <name> -h command. The installed extension list is the authority for what your app supports. If your shell cannot find enconvo, open the app’s CLI Guide and check your installed app version and command-line setup.

Call the local API

The app serves each route at http://localhost:54535/api/<extension>/<route>. Send a POST with a JSON body:
Open Settings → APIs and click Check APIs to inspect the available routes and request schemas, with an example for each. Use the schema for your installed build when writing an integration; route parameters can change as extensions evolve. For an AI client that only needs knowledge-base retrieval, use the dedicated Knowledge Base MCP connection instead of exposing the general local API. Treat local API and shell access as powerful capabilities: commands can read or modify local data according to their implementation. Keep scripts explicit about the command, input, and destination.

Build on it

Developing Extensions

Build a command or a Local API route

Knowledge Base MCP

Give another AI client your knowledge bases