Browse MCP resources and prompts
Resources
Section titled “Resources”mcp-tui --url http://127.0.0.1:8931/mcp resource listmcp-tui --url http://127.0.0.1:8931/mcp resource get acme://kb/getting-started.mdA binary resource is described, not dumped:
mcp-tui --url http://127.0.0.1:8931/mcp resource get acme://brand/logo.pngContent: Type: image/png Binary content: 223 bytes (base64 with --format json)
Served by: acme-support-desk 1.4.0
Cache: fetched · ttl 0s · publicWith --format json the blob comes out base64-encoded, as on the wire. The
Cache line shows how the SDK served the read on 2026-07-28 (SEP-2549): a
repeated read inside the server’s ttlMs is answered from the client cache.
URI templates and completion
Section titled “URI templates and completion”mcp-tui --url http://127.0.0.1:8931/mcp resource templatesmcp-tui --url http://127.0.0.1:8931/mcp resource complete 'acme://tickets/{id}' id=T-104resource complete asks the server’s completion/complete for values of a
template variable and prints them as JSON ("values": ["T-1040", "T-1041", …]).
Prompts
Section titled “Prompts”mcp-tui --url http://127.0.0.1:8931/mcp prompt get triage_ticketArguments: • ticket_id (required): e.g. T-1041 • tone: friendly (default), formal or apologeticArguments are listed in the order the server declared them. Complete a value,
then render the prompt with arguments given as key=value, the same form
tool call takes:
mcp-tui --url http://127.0.0.1:8931/mcp prompt complete triage_ticket tone=fmcp-tui --url http://127.0.0.1:8931/mcp prompt execute triage_ticket ticket_id=T-1041 tone=apologeticText content prints as text; embedded resources and images print as JSON.