Register the molecule MCP server with Claude Code, Codex, Cursor, and any MCP client: the full package, template, and project surface as tools.
npx mlcl setupSetup asks whether to set up every project on this machine or just this one, and which agents, then registers the server with each (Claude Code, Codex, Cursor, Gemini CLI, Copilot, OpenCode, Devin/Windsurf, Kiro, Amp, Zed, Crush, Trae, Cline, Junie) along with the Molecule skills and conventions, and prints what it wrote. For the server alone in one agent, run mlcl mcp install --agent <name>. Any other MCP client takes the stdio command npx -y molecule-mcp.
A hosted endpoint needs no local install at all: point any MCP client at https://mcp.molecule.dev/mcp. It serves the read-only discovery tools: search_packages, list_templates, read_package_doc, and the conventions resource, no login required. The full surface (scaffolding, deploys, sandboxes, your projects) runs locally and uses your own login.
| Tool | Purpose |
|---|---|
search_packages | find @molecule/* packages by capability |
list_templates | the 100+ 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_project | typecheck, lint, build, and test the project’s own checks |
check_env_vars / set_env_var / … | inspect and manage the project’s env |
deploy_project / deploy_status / list_deploys / cancel_deploy | ship and watch, the IDE’s pipeline |
sandbox_status / sandbox_start / sandbox_stop / sandbox_restart / sandbox_exec | boot, stop, and run commands in the project sandbox |
project_logs | the deployed app’s runtime logs |
db_info / db_tables / db_query | inspect and SELECT against the project database |
domain_list / domain_add / domain_verify / domain_remove | custom domains end to end |
list_projects / create_api_key | project admin |
embed_text, translate, web_search, … | the capability services |
74 tools in all. The exact list on your install: ask the client for its tool list. Beyond tools, the server exposes one resource, molecule://conventions: the conventions in a single page.
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. For unattended use, set MOLECULE_TOKEN to a personal API token in the server’s environment instead.