Skip to content
Vitrino docs

MCP servers

MCP (Model Context Protocol) servers give Claude tools beyond the built‑in set — a browser, a database, an issue tracker. Vitrino reads the servers your Claude Code configuration already defines; there is nothing to set up separately.

Which servers are connected

The MCP menu beside the message box lists the servers for the session and their state. The session details row at the top of a transcript also records what was connected when it started.

MCP tool rows

An MCP tool is named mcp__<server>__<tool>. Vitrino renders it as a row with the server as a chip and the tool in readable words — mcp__playwright__browser_click reads as Browser click from playwright.

Short arguments sit on the header line; longer input is collapsed behind Input. Results are shown by what they are:

  • Text — collapsed with a line count.
  • JSON — pretty‑printed and syntax highlighted.
  • Images — as thumbnails you can open full size.
  • Resource links — as links, with the server's description where it gave one.

Raw input and raw output are always one click away.

Elicitations: when a server asks you something

A server can ask the user directly. Vitrino pins that as a card, like a permission request, in one of three shapes:

  • A page to open — usually signing in. The card shows the URL and asks first; nothing opens until you agree, because the server waits for the page to complete.
  • A form — built from the schema the server sent, with the fields it asked for and their validation.
  • The raw schema — when Vitrino cannot build a form from what was sent. You can read it and decline. Vitrino never guesses at a schema it does not understand.

Every elicitation can be declined.

Once answered, it becomes a row recording the server, the request, and how it ended.

MCP prompts

A server can also offer prompts, which appear in the / palette as mcp__server__prompt, grouped under an MCP label.

Deferred tools

Where a server exposes many tools, Claude Code may defer loading their definitions until they are needed, fetching them with ToolSearch. When that happens you will see a Loaded tools row saying which were brought in. It is not an error; it is how a large tool set stays out of the context window until it is wanted.