sj dZddlZddlmZmZddlmZmZdZ dde d e d e d eed e f d Z dddddddgddddddddgddZ ej dde dddS)uPropose an MCP server to the user as an inline card in the desktop chat. The card (install / enable / authorize + decline) lives in the desktop renderer, so this tool round-trips through the gateway's blocking-prompt bridge — the same one ``clarify`` uses: tui_gateway emits ``mcp.setup.request``, the renderer walks the user through the flow via the existing REST endpoints (catalog install, enable, OAuth), and answers with ``mcp.setup.respond`` once the flow settles. This module is just schema + a thin dispatcher over the platform-injected callback. Lives in the ``desktop_ui`` toolset, which the GUI gateway enables only for desktop-sourced sessions — on every other surface the agent falls back to ``hermes mcp install `` in the terminal. N)CallableOptional)registry tool_error)installenable authorizerserveractionreasoncallbackreturnc|tdS|pd}|stdS|pd}|tvr+tddtdS ||||pd}n)#t $r}td |cYd}~Sd}~wwxYw|st jd |d d d S t jt j|d S#ttf$r)t jdt|dd cYSwxYw)zFAsk the desktop GUI to run an MCP setup flow; return its JSON outcome.Nzsetup_mcp is only available in the Hermes desktop app. Use the terminal instead: `hermes mcp install ` for catalog entries, `hermes mcp login ` for OAuth.r uDserver is required — the catalog or config name of the MCP server.rzaction must be one of z, .zMCP setup flow failed: unansweredzqThe user did not respond to the setup card. Do not retry immediately; continue without the server or ask in chat.)statusr noteF) ensure_asciierror)rdetail) rstriplower_ACTIONSjoin Exceptionjsondumpsloads TypeError ValueErrorstr)r r r rnamerawexcs 8/home/agent/.hermes/hermes-agent/tools/setup_mcp_tool.pysetup_mcp_toolr's 3   Lb   ! !D b`aaa! ( ( * * 0 0 2 2F XI499X3F3FIIIJJJ;htVfl%9%9%;%;<< ;;;9C99::::::::;   z&O       Wz$*S//>>>> z "WWWzWCAAPUVVVVVVWs0!B88 CCCC>'D&&7E E  setup_mcpuPropose an MCP server to the user as an inline consent card in the Hermes desktop chat. The card lets them install a catalog entry, re-enable a disabled server, or run an OAuth login — right there, without opening the Capabilities tab — and blocks until they act or decline. Use when the user asks to add/set up an MCP (e.g. "add the linear mcp"), or when a task clearly needs one that is missing or unauthorized. Never call it twice for the same server after a decline. Returns JSON {status: installed|enabled|authorized|declined|unanswered|error, server, detail?, tools?}. On declined/unanswered, continue without the server. Catalog names: run `hermes mcp catalog` in the terminal to list them.objectstringzaThe server's catalog name (for install) or its name in mcp_servers config (for enable/authorize).)type descriptionzinstall: add a catalog entry (prompts for any required keys). enable: re-enable a disabled configured server. authorize: run the OAuth browser flow for a configured server. Defaults to install.)r+enumr,zrOne short sentence shown on the card: why this server helps right now (e.g. "To read the JIRA ticket you linked").)r r r )r+ propertiesrequired)r#r, parameters desktop_uic t|dd|dd|dd|dS)Nr r r rr r)r r r r)r'get)argskws r&r6sW~xx"%%xx),,xx"%% ##    u🔌)r#toolsetschemahandleremoji)r rr N) __doc__rtypingrrtools.registryrrrr"r'SETUP_MCP_SCHEMAregisterr7r&rBsr   %%%%%%%%//////// -#' .W.W .W .W .Wx .W  .W.W.W.Wd  (!A!:::3  !!%  6J;..b            r7