Overview
registerAppTool is a convenience wrapper around the MCP SDK’s server.registerTool() that normalizes UI metadata for compatibility across hosts. Use it instead of registerTool when your tool should render a View or when it needs MCP App visibility metadata.
Signature
Parameters
McpServer
required
The MCP server instance.
string
required
Tool name/identifier.
McpUiAppToolConfig
required
Tool configuration. Extends the standard MCP
ToolConfig with a required _meta field containing UI metadata.string
Human-readable tool title.
string
Tool description for the model.
ZodRawShape | AnySchema
Zod schema or JSON Schema for tool arguments.
ZodRawShape | AnySchema
Zod schema or JSON Schema for tool output.
ToolAnnotations
Standard MCP tool annotations, such as
readOnlyHint, destructiveHint, idempotentHint,
and openWorldHint. See Tool Annotations.object
required
UI metadata linking this tool to a resource, controlling tool visibility, or both. See _meta Reference below for full details.
McpUiToolMeta
required
string
URI of the UI resource to display (e.g.,
"ui://weather/view.html"). Required for tools that render a View. Must match a URI registered via registerAppResource.McpUiToolVisibility[]
Who can access this tool. Default:
["model", "app"]. See visibility below.ToolCallback
required
Tool handler function. Receives parsed arguments and returns a
CallToolResult.Usage
Basic tool with UI
Read-only tool annotations
Addannotations when a UI tool is read-only, destructive, idempotent, or calls external systems. Hosts can use these hints for review UI and tool-calling behavior.
App-only tool (hidden from model)
Setvisibility: ["app"] for tools that should only be callable from the View, such as polling, pagination, or UI-driven server interactions. Omit resourceUri when the helper does not render a new View:
Model-only tool
Setvisibility: ["model"] for tools that the model can call but the View cannot:
_meta Reference
See Tool _meta for the complete reference on resourceUri, visibility, host behavior rules, and metadata normalization.
See Tool Annotations for when to set readOnlyHint, destructiveHint, idempotentHint, and openWorldHint.
See Tool and Resource Contract for how tool metadata, resource metadata, content, and structuredContent fit together.