List plugins

Reports what this deployment actually mounted: every subsystem the composition root declared and whether it is switched on.

GET /v1/tool/plugins

Tool → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/tool/plugins`
Method	`GET`
Operation	`get_tool_plugins`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Reports what this deployment actually mounted: every subsystem the composition root declared and whether it is switched on. A plugin here is MOUNTED CODE that extends the deployment's own surface — not a tool an agent calls — so this is an inventory and not a tool source. It is read off the same boot snapshot every traced request resolves its subsystem label against, so it cannot drift from what is serving. Enabled-only by default, because a caller asking what this deployment can do wants what is running; ?all=true adds the configured-but-off ones.

Request

1 field.

Field	In	Type	Required	Description
`all`	query	string	—	All includes the configured-but-disabled subsystems too, but only when it is exactly the string "true".

Response

Status	Body	Meaning
`200`	tool.pluginMountList	ok
`default`	problem-details	refused

200 body — 4 fields.

Field	In	Type	Always	Description
`plugins`	body	tool.pluginMount[]	—	Plugins is every subsystem the composition root declared, filtered to the enabled ones unless all=true.
`plugins[].enabled`	body	boolean	—	Enabled is whether this subsystem is switched on in this deployment.
`plugins[].name`	body	string	—	Name is the subsystem's name, the same label a traced request resolves to.
`plugins[].prefixes`	body	string[]	—	Prefixes are the URL prefixes this subsystem serves.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo tool plugins get

.ts

.py

.go

.rs

.java

import { Configuration, ToolApi } from 'hanzoai';

const api = new ToolApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getToolPlugins();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ToolApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ToolApi(client).get_tool_plugins()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ToolAPI.GetToolPlugins(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, tool_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = tool_api::get_tool_plugins(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ToolApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ToolApi(client).getToolPlugins();

curl https://api.hanzo.ai/v1/tool/plugins \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches tool through the tool tool, which names its 17 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_tools"
         }
       }
     }'

Tool API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList authored — GET /v1/tool/plugins/authored NextList authored — GET /v1/tool/skills/authored