MCP server for MooStack. Manage your studio conversationally via Claude
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"moostack-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# moostack-mcp An MCP server that lets a MooStack studio owner manage their studio conversationally through Claude Desktop or Claude Code — no dashboard required. It's a thin client: every tool call is proxied to your studio's MooStack backend over HTTPS. ## Requirements - Python 3.11+ - A MooStack account (email + password) that owns or belongs to at least one studio ## Install With [uv](https://docs.astral.sh/uv/) (recommended): ```sh uv tool install git+https://github.com/thekaushikls/moostack-mcp ``` Or with pip: ```sh pip install git+https://github.com/thekaushikls/moostack-mcp ``` ## Set up ```sh moostack-mcp setup ``` This will: 1. Ask for your MooStack email, password, and backend URL (press Enter to accept the default). 2. Validate the credentials against the backend. 3. Save them to `~/.moostack/config.json` (created with `0600` permissions — readable only by you). 4. Offer to auto-configure Claude Desktop by adding this server to `claude_desktop_config.json`. Restart Claude Desktop afterwards and it will pick up the new server. ### Manual Claude Desktop setup If you skip auto-configure, or you're on an OS it doesn't recognize, add this to your `claude_desktop_config.json` yourself (merge it into the `mcpServers` object if one already exists): ```json { "mcpServers": { "moostack": { "command": "moostack-mcp", "args": ["serve"] } } } ``` Config file locations: - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` - Linux: `~/.config/Claude/claude_desktop_config.json` ## What you can do with it **Your account & studios** - `list_my_studios` — the studios you own or belong to, and your role in each - `get_my_profile` / `update_my_profile` — view or edit your account details - `list_members` — your studio's member roster **Classes & pricing** - `list_offerings` — every class you've set up, with its pricing tiers - `create_offering` / `upda…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.