Connect Claude Code

Claude Code can call GGUI’s tools, but it isn’t an MCP Apps host: it doesn’t mount the interface GGUI builds, so no card appears in Claude Code. Claude reads the tool result and tells you about it in text. To see and use the generated interface, connect the same account in Claude Desktop or claude.ai.

Add the server

claude mcp add --transport http ggui https://mcp.ggui.ai

That adds GGUI for the current project only. Add --scope user to make it available in every project.

Sign in

Claude Code doesn’t open the sign-in on its own. Run /mcp inside Claude Code, pick ggui, and follow the steps in your browser: sign in at the GGUI console and click Approve. The console creates the access key and hands it to Claude Code; there’s nothing to copy.

What you get

• The tools work. Claude can negotiate, render and read results, and each render is made under your account and charged like any other.
• No inline card. Claude Code ignores the interface GGUI attaches to each result, so you see Claude’s description of it instead.
• Long tool descriptions are trimmed. Claude Code cuts each MCP tool description, and the server’s instructions, to 2,048 characters. GGUI’s tools still work at that length; to lift the limit, set the CLAUDE_CODE_MAX_MCP_DESCRIPTION_LENGTH environment variable higher before starting Claude Code.

Other hosts

Connect other MCP hosts covers Cursor, VS Code, Goose and the rest, and the compatibility matrix shows which ones render cards.