Releases: mattzz123/mm-mcp-releases
Release list
v0.7.0 — Install-code device authorization (token no longer in chat)
Security fix: the long-lived org:agent token no longer enters the agent chat.
The dashboard at /dashboard/integrations/mm-mcp now generates a single-use INSTALL CODE (mmi_…, 10-minute TTL). The mm-mcp binary exchanges it locally via TLS for the actual token, then writes the MCP client configs — UTF-8 without BOM, Microsoft Store (MSIX) path on Windows, atomic temp-file+rename with 0600 permissions on Unix.
New: `mm-mcp setup`
```
mm-mcp setup --code mmi_… --api-url https://.t.mothershipmethod.cloud
```
Detects every installed MCP client (Claude Desktop, Claude Code, Cursor), writes the config from a durable per-user path, validates the token via /v1/auth/me. No PowerShell BOM trap, no MSIX virtualized-path miss, no token in argv/chat.
Install
The dashboard renders the per-OS install command directly — usually one line in your terminal. If you prefer manual install:
| OS / arch | Asset |
|---|---|
| macOS Apple Silicon | mm-mcp-darwin-arm64 |
| macOS Intel | mm-mcp-darwin-amd64 |
| Linux x86_64 | mm-mcp-linux-amd64 |
| Linux arm64 | mm-mcp-linux-arm64 |
| Windows x86_64 | mm-mcp-windows-amd64.exe |
SHA256SUMS attached. Verify with `sha256sum -c SHA256SUMS`.
Upgrading
If you already had a previous mm-mcp installed via a 30-day token: it still works. To migrate, generate a new install code from the dashboard and re-run `mm-mcp setup` — the binary will overwrite the relevant config entries in place, preserving any other MCP servers you have configured.
Built from
`mothership-method@42ff7d6` — design review GO, code review GO (0 P0/P1, 3 P2 + 4 P3 remediated), remediation review GO.
v0.6.0 — project hierarchy (parent / sub-projects)
Optional project hierarchy. mm_project_create takes an optional parent
(slug or UUID, same scope) to nest a project under another (e.g. clients under
a company). mm_project_update takes parent (re-parent) and clear_parent
(back to top level); cycles, cross-scope parents and excessive depth are
rejected. Instructions bumped to 3.1.0 — active_projects now carries
parent_id / parent_slug / child_count.
Update: re-run the installer (pulls this latest), clear quarantine on macOS,
relaunch your MCP client.
v0.5.0 — mm_project_update fix (If-Match)
Fixes mm_project_update, which previously failed on every call because the
client did not send the If-Match header the backend requires for versioned
writes. Project summary/status updates from your agent now work.
Adds an optional expected_version parameter for explicit conflict protection
(pass the version you saw in mm_project_get; omit it to let the tool resolve
the current version automatically). No other tools changed.
To update: re-run the installer (it pulls this latest build), then on macOS
clear quarantine and relaunch your MCP client:
xattr -d com.apple.quarantine /mm-mcp
v0.4.0 — Documents + References Layer
Per-project markdown documents + structured ID references. New MCP tools: mm_document_, mm_ref_. Instructions auto-update from server (no reinstall needed for protocol changes).
v0.3.0 — Dynamic instructions (no more reinstalls)
Big change: future updates land automatically
Starting with this release, mm-mcp fetches the MCP server instructions from your tenant API on every startup. This means:
- We can update the agent's behavior, add new tools, fix bugs in protocol guidance — and you see it on the next Claude Desktop session, without reinstalling.
- The binary keeps a bundled fallback in case the server is unreachable.
After this update, never reinstall again (for protocol changes).
Install (macOS Apple Silicon)
```bash
sudo curl -L -o /usr/local/bin/mm-mcp https://github.com/mattzz123/mm-mcp-releases/releases/latest/download/mm-mcp-darwin-arm64
sudo chmod +x /usr/local/bin/mm-mcp
```
Install (macOS Intel)
```bash
sudo curl -L -o /usr/local/bin/mm-mcp https://github.com/mattzz123/mm-mcp-releases/releases/latest/download/mm-mcp-darwin-amd64
sudo chmod +x /usr/local/bin/mm-mcp
```
After install, restart Claude Desktop completely.
v0.2.0-vault — Vault + Generic HTTP Caller
Mothership Method MCP — Vault release
What's new
- Encrypted secrets storage (AES-256-GCM envelope + Curve25519 sealed-box)
- Generic HTTPS proxy with anti-SSRF (IPv4+IPv6 deny list, DNS rebinding protection)
- Per-secret destination host allowlist
- New MCP tools: mm_secret_list, mm_tool_list, mm_tool_invoke
- Bootstrap now includes available_secrets metadata
- Updated server instructions teaching the agent the new http/call pattern
Install (macOS Apple Silicon)
sudo curl -L -o /usr/local/bin/mm-mcp https://github.com/mattzz123/mm-mcp-releases/releases/latest/download/mm-mcp-darwin-arm64
sudo chmod +x /usr/local/bin/mm-mcpInstall (macOS Intel)
sudo curl -L -o /usr/local/bin/mm-mcp https://github.com/mattzz123/mm-mcp-releases/releases/latest/download/mm-mcp-darwin-amd64
sudo chmod +x /usr/local/bin/mm-mcpAfter install, restart Claude Desktop completely.
v0.1.0-alpha — first mm-mcp release
v0.1.0-alpha — First public release
This is the first public release of mm-mcp, the official Model Context Protocol bridge for Mothership Method.
What is mm-mcp?
mm-mcp connects your AI client (Claude Desktop, Cursor, VS Code, etc.) to your Mothership Method workspace, giving your AI agent persistent organizational memory across sessions.
Requirements
- A Mothership Method account
- An MM_TOKEN from your workspace dashboard → Integrations → MCP
Install
# macOS Apple Silicon
curl -L -o /usr/local/bin/mm-mcp \
https://github.com/mattzz123/mm-mcp-releases/releases/latest/download/mm-mcp-darwin-arm64
chmod +x /usr/local/bin/mm-mcp
# macOS Intel
curl -L -o /usr/local/bin/mm-mcp \
https://github.com/mattzz123/mm-mcp-releases/releases/latest/download/mm-mcp-darwin-amd64
chmod +x /usr/local/bin/mm-mcp
# Linux x86_64
curl -L -o /usr/local/bin/mm-mcp \
https://github.com/mattzz123/mm-mcp-releases/releases/latest/download/mm-mcp-linux-amd64
chmod +x /usr/local/bin/mm-mcpConfigure (Claude Desktop example)
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"mothership": {
"command": "mm-mcp",
"env": {
"MM_TOKEN": "your-token-here",
"MM_API_URL": "https://your-workspace.t.mothershipmethod.cloud"
}
}
}
}Verify integrity
SHA256 checksums are in SHA256SUMS.txt. Verify before running:
sha256sum mm-mcp-darwin-arm64
# Compare against SHA256SUMS.txtKnown limitations (alpha)
- Single-tenant per binary invocation
- No automatic updates
- GPG signing coming in a future release
Support
Contact: onboarding@mothershipmethod.cloud