MCP server
Register the molecule MCP server with Claude Code, Codex, Cursor, and any MCP client — the full package, template, and project surface as tools.
Install
npx mlcl mcp installThe installer registers the server with your harness — Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Windsurf, Kiro, Trae, Zed, Amp, Crush, Cline, VS Code, and any MCP client — and prints what it wrote. Re-run it after upgrading mlcl to refresh the registration.
A hosted endpoint needs no local install at all: point any MCP client at https://mcp.molecule.dev/mcp.
The tools
| Tool | Purpose |
|---|---|
search_packages | find @molecule/* packages by capability |
list_templates | the 152 flagship apps |
scaffold_project | create a project from a template or custom stack |
add_package / swap_provider | wire a capability in / change the provider |
read_package_doc | a package’s generated README |
check_env_vars / set_env_var / … | inspect and manage the project’s env |
deploy-family + check_project | ship and verify (typecheck, lint, build, tests) |
list_projects / create_api_key | project admin |
sandbox / db / logs surfaces | operate a running project |
embed_text, translate, web_search, … | the capability services |
The exact list on your install: ask the client, or npx mlcl mcp install --help. Beyond tools, the server exposes one resource — molecule://conventions, the molecule way in a single page.
Accounts
Read-only discovery works without an account. Cloud operations (deploy, projects, sandboxes) authenticate with login / login_poll — a device-code flow: the tool returns a URL, you approve in the browser, done. whoami and list_devices / revoke_device manage sessions.