Muse-Chat-MCP
Related Servers
Alternatives to Muse-Chat-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets any MCP host or OpenAI-compatible client chat with Meta's Muse (muse.ai Hatch) agent by driving your own logged-in Chrome, exposing tools for status, login, new chat, prompting, and reading replies. It also serves an OpenAI-compatible HTTP endpoint with real SSE streaming and prompt-injected tool calling, plus a small CLI for one-shot generation.1159MIT
- AlicenseNot gradedqualityCmaintenanceExposes authorized ChatGPT, DeepSeek, Kimi, and Grok web sessions to agents as MCP tools, including chat and local file attachments over HTTP or stdio.7MIT
- FlicenseNot gradedqualityCmaintenanceEnables a local MCP server to control an authenticated Chrome browser for interacting with Google Search, Gemini, ChatGPT, Claude, and DeepSeek, including web search and image generation without per-provider API keys.-
- AlicenseNot gradedqualityBmaintenanceMCP server that turns one authenticated ChatGPT browser page into a bounded MCP server, exposing tools for creating, listing, searching, exporting, sending, editing chats and downloading media via a CDP driver.MIT
- AlicenseBqualityCmaintenanceEnables browser control through your existing signed-in Chrome profile, letting MCP clients like Claude Code manage tabs, navigate, inspect pages, and perform real user interactions via tool calls. Works with any model backend without needing Playwright or a fresh browser profile.21MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to drive ChatGPT's web interface through a built-in persistent browser, requiring only a single manual login. Prompts are sent through temporary incognito chats and the captured answer text is returned as tool results, along with live model listing, login/status probing, and optional HTTP transport.83Apache 2.0
TDQS
Scored across 11 tools
Each tool targets a distinct action (new/list/open/read/send/close) on the Muse chat domain. Minor overlap: muse_read_last is essentially a subset of muse_read_chat, and muse_read_chat's optional 'open a chat first' behavior duplicates part of muse_open_chat, but descriptions clarify the intent.
All tools share a consistent muse_ snake_case prefix, which makes the set highly readable. A few names are noun-only (muse_chats, muse_media, muse_status) rather than verb_noun, a minor deviation from the dominant pattern.
11 tools is well within the ideal range and each one maps to a clear browser-automation need (lifecycle, auth, reading, sending, diagnostics). Nothing feels redundant or bloated.
The surface covers the full chat lifecycle: auth (status/login), navigation (new/open/list/close), reading (read_chat/read_last/media), and sending (chat), plus diagnostics. Gaps are minor—no delete/rename/archive chat operations—but core workflows are fully covered.