Muse-Chat-MCP
Related Servers
Alternatives to Muse-Chat-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables any MCP client or OpenAI-compatible application to use Meta Muse through a logged-in Chrome session, with tools for chat, attachments, session management, media retrieval, streaming, and tool-call compatibility.112MIT
- 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
- AlicenseAqualityCmaintenanceMCP server that drives chat.sakana.ai via headless Chrome with persistent sessions. Enables AI assistants to interact with Sakana AI chat through tools like session management, with ToS gate and browser automation.540 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI assistants drive your real, already-logged-in Chrome through a browser extension, so agents can read, click, type, navigate, screenshot, inspect network traffic, and manage cookies or storage on pages that require existing sessions. It works without opening a remote-debugging port and keeps all communication on your machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the real Chrome browser you already have open, so agents can read logged-in pages, click, fill forms, take screenshots, and inspect tabs, cookies, and network traffic. All communication stays on your machine, with no debugging port or manual cookie copying required.1 npmISC
TDQS
Scored across 11 tools
Most tools have distinct purposes, but muse_chat (send prompt) and muse_chats (list chats) are easy to confuse due to near-identical names. muse_read_chat, muse_read_last, and muse_media also have some overlap in reading chat content, though descriptions clarify the boundaries.
All tools use the muse_ prefix with snake_case, which is highly consistent. Minor deviations exist in verb/noun patterns (e.g., muse_status, muse_media, muse_chats are noun-like, while others are verb-led), but the overall convention remains readable and predictable.
Eleven tools is well-scoped for a browser-automation MCP that manages login, chat navigation, reading, sending, media extraction, and diagnostics. Each tool appears to earn its place without excessive fragmentation.
The surface covers the core chat lifecycle: status/login, new/open/close, list/read/send, media extraction, and diagnostics. Minor gaps exist around chat management (e.g., delete, rename, or search), but these are not