Skip to main content
The Inspector exports chat UI components from @mcp-use/inspector/client for applications that want to embed the Inspector chat experience in their own React UI. The /client entry intentionally keeps its React and UI runtime dependencies external. Applications importing it must declare the optional peers they use; ordinary mcp-use projects do not install this UI graph because the standalone Inspector already bundles it. Use ChatTab when you want the full chat surface. Use lower-level components such as MessageList only when you need to own the surrounding layout.

ChatTab

ChatTab renders the Inspector chat UI for one connected MCP server.

Props

Controlled skills and system prompt

Pass skillSelection to show the native Add skills picker and removable skill chips inside the composer. The picker uses the complete connection.skills catalog, so deselected skills remain available to re-enable.
ChatSkillSelection is exported from @mcp-use/inspector/client: For client-side chat, only selected skills are advertised to the model and available through the skill-reading tools for the next turn. An empty set disables all skills. Omitting skillSelection keeps automatic discovery of every advertised skill and hides the selection UI. Server-side chat keeps its request body host-owned: use body to include the selected URIs in the shape expected by your backend. systemPromptProvider uses the existing compact System Prompt control in the input toolbar. Its prompt and savePrompt fields can read and persist your application’s chat settings; optional isLoading, isSaving, and disabled fields describe the provider state. Without a provider, Inspector uses its local system-prompt storage.

Lower-level components

Use lower-level exports when ChatTab owns too much UI for your application.
When rendering widgets inside messages, pass serverBaseUrl from the MCP connection URL so widget resources resolve against the correct server origin.