Muse-Chat-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUSE_CDP | No | attach to an existing Chrome at this URL (e.g. http://127.0.0.1:9222) instead of launching | |
| MUSE_URL | No | app URL | https://muse.ai/ |
| MUSE_CHANNEL | No | chrome or msedge | chrome |
| MUSE_HEADLESS | No | run headless (log in headed first) | 0 |
| MUSE_SHIM_URL | No | shim base url used by the CLI | http://127.0.0.1:8787/v1 |
| MUSE_SHIM_HOST | No | shim bind host | 127.0.0.1 |
| MUSE_SHIM_PORT | No | shim port (0 disables the shim) | 8787 |
| MUSE_PROFILE_DIR | No | dedicated Chrome profile (holds your login) | ./.muse-profile |
| MUSE_SHIM_MODELS | No | advertised model ids | muse-spark-1.3,muse-spark-1.3-contributor,muse |
| MUSE_CLI_AUTOSTART | No | disable the CLI auto-starting a shim | 0 |
| MUSE_SHIM_TIMEOUT_MS | No | default shim request timeout | 240000 |
| MUSE_STREAM_QUIET_MS | No | streaming stability window (skip mid-message draft rewrites) | 600 |
| MUSE_LAUNCH_TIMEOUT_MS | No | launch / navigation timeout | 60000 |
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
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