infinity-musebird
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
infinity-musebird
Use Muse as a subagent inside Claude Code, Codex, or OpenCode.
Type /inf-muse build me a thing; Muse does the work in its own sandbox, and the
results land in your repo on a review branch.
Unofficial. Not affiliated with Meta or Muse.
curl -fsSL https://raw.githubusercontent.com/M1778/infinity-musebird/main/install.sh | bashThen click through one Muse sign-in. That is the whole setup: the installer registers
the MCP server and both skills in every harness it finds, and musebird doctor tells
you what is green.
Windows (PowerShell):
irm https://raw.githubusercontent.com/M1778/infinity-musebird/main/install.ps1 | iexPrefer not to pipe a script into a shell? Download it, read it (~60 lines), run it. Or
uvx infinity-musebird install. Every real action lives in Python so it is testable
and identical across platforms.
Release assets ship with SHA256SUMS; verify with
sha256sum -c SHA256SUMS --ignore-missing. Each install.sh pins the release tag it
ships in, so the script and the package it installs always match.
Before you use this, read DISCLAIMER.md. This automates a web session on your own account. That may violate Muse's terms of service. Anything you send leaves your machine and is processed in a third-party sandbox. Returned code is untrusted: review it before running or merging.
The disclaimer in full, in brief:
Unofficial. Not affiliated with, endorsed by, or sponsored by Muse or its operators. "Muse" and related names are trademarks of their respective owners.
Terms of service. This tool automates a web session on your own account. Automating a website may violate its terms of service and could result in rate limiting, suspension, or termination of your account. You are solely responsible for reading and complying with Muse's terms and for any consequences. This project does not and will not support multi-account rotation or circumventing usage limits.
Your data. Anything you send (source code, files, prompts) is transmitted to a third-party service and processed in its sandbox. Do not send secrets, regulated data, or code you are not permitted to share. Use
.musebirdignore.Credentials. The session is stored locally (OS keychain or a restricted-permission file). Treat it like a password;
musebird logoutdeletes it.Untrusted output. Review all returned code. This tool never auto-executes it.
No warranty. MIT, "as is". It relies on an unofficial interface that can break at any time.
What you get
Command | What it does |
| Muse works in its sandbox; you get a branch to review |
| Muse fans out to N subagents, cross-reviews, merges |
The harness model only orchestrates: it reads the skill, calls MCP tools, relays progress, and reviews the diff. Your harness can be running any model.
Ten MCP tools: muse_status, muse_login, muse_job_start, muse_job_status,
muse_job_events, muse_job_message, muse_job_cancel, muse_files_list,
muse_files_pull, muse_files_push.
Related MCP server: handoff-mcp
Requirements
macOS, Linux, or WSL (Windows native is supported through PowerShell).
Chrome, Edge, or Chromium. Playwright's Chromium is downloaded only if no system browser is found.
A Muse account in a supported region.
Python is provided by
uv; you do not need to install it.
Manual setup
uv tool install 'infinity-musebird[all]'
musebird install --yes
musebird login
musebird doctorUseful flags:
musebird install --dry-run # print every planned change, write nothing
musebird install --harness claude # limit to one harness
musebird install --skip-login # log in later
musebird uninstall # remove MCP entries + skills we added
musebird uninstall --purge # also delete the session, jobs, and logs
musebird update # refresh skills and config after an upgradeHow it works
The skill checks
muse_statusand decides which files Muse needs (honouring.musebirdignore, secret scan, and a first-upload confirmation).muse_job_startreturns a job id immediately. A detached worker drives a real browser, wakes the Muse sandbox VM, sends the task plus a prompt contract, and streams events to disk.Every job runs in its own Muse side chat, never your main conversation, and the driver refuses to run if it cannot verify that isolation. Muse writes output to
out/with aMANIFEST.json(sha256 per file) and prints a completion sentinel.muse_files_pullverifies every hash and commits the result tomusebird/<job_id>— never into your working tree.You review the diff and decide whether to merge.
If a job asks a question, the job state becomes needs_input and your harness asks
you. Nothing auto-approves anything.
Reviewing results
musebird jobs list
musebird jobs show <id> --events
git diff HEAD...musebird/<id>
git merge musebird/<id>Files also remain in .musebird/landing/<id>/ for inspection. Nothing is executed.
Configuration
Variable | Purpose |
| state directory (default |
| project root override |
|
|
.musebirdignore in your project uses gitignore syntax and is additive to safe
defaults (.env*, keys, .git, node_modules, cookie files, data/).
Development
uv venv && uv pip install -e '.[all]'
uv pip install pytest pytest-asyncio ruff pyright
.venv/bin/python -m pytest # 71 tests, no network, no accountThe entire suite runs against the mock driver. Live tests are marked @pytest.mark.live
and skipped by default; run them deliberately against your own account to check that
Muse's selectors still match:
MUSEBIRD_LIVE=1 .venv/bin/python -m pytest tests/test_live.py -v -s./scripts/check.sh is the full gate (lint, types, wheel, tests, secret scan).
See CONTRIBUTING.md and docs/HARNESS_NOTES.md
for the verified harness/Muse details.
Documentation
docs/ARCHITECTURE.md — components, job lifecycle, landing
docs/HARNESS_NOTES.md — verified config formats and dates
docs/TROUBLESHOOTING.md — every failure, with a fix
SECURITY.md — reporting, data flow, what is stored where
Credits
Inspired by www222fff/muse2api (MIT), which does the opposite job: exposing Muse as an OpenAI-compatible API. The browser automation approach, cookie handling, VM-wake confirmation, and quota parsing derive from it. See NOTICE.
License
MIT. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Shared long-term memory & Stop-hook task handoff across Claude Code, Codex, Cursor, and mobile.
Coordination hub for AI coding agents: message teammates, ask humans, audit every event.
Multiplayer for the coding agents your team already uses: shared tasks, decisions, skills and tools.
Your AI mind directs coding agents; work reviewed against your memories: Claude Code, Codex, Cursor
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Codex to delegate tasks to Claude Code, allowing Claude to investigate, edit, and verify changes in the repository with background job management.MIT
- AlicenseAqualityDmaintenanceEnables Claude to delegate tasks to external coding agents (Codex or Antigravity) for independent reviews, separate quota usage, and async processing.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code and Claude Desktop to delegate coding tasks to any model available in OpenCode while Claude remains the orchestrator, planning work, reviewing diffs, and running tests. Supports synchronous and async delegation, model selection, session continuation, and permission-aware execution.6MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate software-engineering tasks to OpenCode agents working in the same workspace.727 npm1MIT