Muse-Chat-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| muse_statusA | Report whether the Muse browser is running, whether you are logged in to muse.ai, and whether the chat composer is ready. |
| muse_loginA | Open muse.ai in the dedicated Chrome window and wait for Meta sign-in to complete. Use when muse_status reports loggedIn=false. |
| muse_new_chatA | Start a fresh Muse thread (navigates to the home composer). |
| muse_chatA | Send a prompt to Muse and return the assistant reply once streaming finishes. Uses your own logged-in session and token quota. |
| muse_read_lastA | Return the most recent assistant message from the current thread without sending anything. |
| muse_chatsA | List the chats in the Muse sidebar (Main chat, Channels, Side chats) with an active flag. Optionally filter by title. |
| muse_open_chatA | Open a specific Muse chat so later reads/sends target it (instead of the main chat). |
| muse_read_chatA | Return the messages of a chat (all roles) without sending anything. Optionally open a chat first. |
| muse_mediaA | Extract image/video/attachment links from a chat (Muse replies with share links for generated media). Optionally download them. |
| muse_dump_domB | Diagnostics: element counts and transcript HTML. Use if selectors stop matching after a Muse update. |
| muse_closeA | Close the dedicated Chrome window and release the profile. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.