-
Notifications
You must be signed in to change notification settings - Fork 92
Agent UI MCP Server: programmatic UI control for agents #549
Copy link
Copy link
Open
Labels
agentchatChat SDK changesChat SDK changesconsumerBlocks consumer adoption — must ship for the v0.20.0 consumer launch windowBlocks consumer adoption — must ship for the v0.20.0 consumer launch windowdomain:agent-coreFramework, tools, registry, memory, skills, orchestrationFramework, tools, registry, memory, skills, orchestrationelectronElectron app changesElectron app changesenhancementNew feature or requestNew feature or requestmcpMCP integration changesMCP integration changesp0high priorityhigh priorityspec-readyIssue has implementation spec adequate for coding-agent assignmentIssue has implementation spec adequate for coding-agent assignmenttrack:consumer-appHermes-competitor consumer product — mobile-first, voice + messaging + memory + skillsHermes-competitor consumer product — mobile-first, voice + messaging + memory + skills
Metadata
Metadata
Assignees
Labels
agentchatChat SDK changesChat SDK changesconsumerBlocks consumer adoption — must ship for the v0.20.0 consumer launch windowBlocks consumer adoption — must ship for the v0.20.0 consumer launch windowdomain:agent-coreFramework, tools, registry, memory, skills, orchestrationFramework, tools, registry, memory, skills, orchestrationelectronElectron app changesElectron app changesenhancementNew feature or requestNew feature or requestmcpMCP integration changesMCP integration changesp0high priorityhigh priorityspec-readyIssue has implementation spec adequate for coding-agent assignmentIssue has implementation spec adequate for coding-agent assignmenttrack:consumer-appHermes-competitor consumer product — mobile-first, voice + messaging + memory + skillsHermes-competitor consumer product — mobile-first, voice + messaging + memory + skills
Summary
Create an MCP server that wraps the Agent UI REST API so the agent can programmatically control the UI — search past conversations, create sessions, manage tunnels, and manage schedules. This is the agent's interface to the UI, not direct database access.
Source Spec
docs/plans/autonomous-agent-infrastructure.md— Milestone 2Why MCP (Not Direct DB Access)
The Agent UI owns its database (
gaia_chat.db). The agent never touches it directly. Instead, the MCP server wraps REST API endpoints as MCP tools, giving the agent a clean, stable interface.MCP Tools
Session Management
list_sessions(limit, offset)— List chat sessions with title, date, message countcreate_session(title, model, system_prompt)— Create a new sessionget_session(session_id)— Get session detailsupdate_session(session_id, title, system_prompt)— Update sessiondelete_session(session_id)— Delete session and messagesConversation Access
get_session_messages(session_id, limit)— Get messages for a sessionsearch_conversations(query, limit)— FTS across all sessions (NEW endpoint)export_session(session_id, format)— Export as markdown/JSONTunnel Management
start_tunnel()— Start ngrok tunnel, return URL + auth tokenstop_tunnel()— Stop active tunnelget_tunnel_status()— Check tunnel statusSystem
get_system_status()— Health, uptime, model infoImplementation
GET /api/sessions/searchendpoint in Agent UI for conversation FTSFiles
Dependencies
Acceptance Criteria