Ai
The tool catalogue and MCP exposure
Every tool the assistant can call, with the group and tier the settings page renders, and whether an MCP client may currently reach it. Admin only.
curl -X GET "https://example.com/api/ai/tools"{ "tools": [ { "name": "string", "description": "string", "group": "string", "tier": "read", "minRole": "viewer", "mcpDefault": true, "mcpExposed": true } ], "mcpTools": [ "string" ], "mcpExposedCount": 0, "toolCount": 0}List available models GET
The configured provider's model ids, for the settings dropdown. Falls back to a static list when the provider can't be reached. Requires the **viewer** role.
Tool approvals for a local CLI POST
A one-tool MCP server (`approve`) that a local CLI provider asks before it runs a tool, so the person in the Udon conversation can allow or deny the call. Udon gives the CLI a run ticket in the `ticket` query parameter; without a live ticket every call is denied. It authenticates like `/api/mcp` and is not meant for external MCP clients.