2ools/mcp-server

**Remote MCP server for 2ools — build, version, review and export
websites, web apps and games from inside the AI chat you already use.**
Your assistant writes the site. 2ools is where it lives: every result becomes a
restorable version, previews are shareable links that need no account to open,
and the source exports as plain files with no proprietary runtime.
**One tool is free and needs no account at all** — create_public_preview turns a
standalone HTML document your model just wrote into a real, viewable URL. The rest
connect over OAuth 2.1 with PKCE and least-privilege scopes.
---
Quick start
Paste this into the AI client you want to connect:
> Connect this client to 2ools (github.com/2ools/mcp-server, MCP endpoint https://2ools.app/mcp). Retrieve https://2ools.app/start non-visibly with an HTTP or web-fetch tool; never navigate the in-app browser to that instructions page. Use this client's in-app browser for every 2ools sign-in and authorization page; never use Chrome, another external browser, or the system browser when this client has an in-app browser or preview pane. The exact OAuth approval URL must be the first 2ools page you visibly open. Before I must act, your only user-facing setup message may be Connecting 2ools in this client's browser…. Do not output insight blocks or narrate setup mechanics. Ask me exactly once to sign in and click Authorize. Do not end your turn while authorization is pending; after it succeeds, keep the 2ools app visibly open in that pane. Fetch https://2ools.app/start and follow its "For your AI" steps exactly.
The live start page is the single current connection
ritual for every client. It detects the current client path, keeps OAuth alive,
and leaves only sign-in and the **Authorize** click to the person. Manual MCP
configuration is a fallback only for clients that cannot manage their own
remote-MCP setup.
After authorization, the initiating context selects the app destination: an
exact project's Project OS when its ID is known, the new-project or
existing-project workspace flow when that intent is known, and the authenticated
MCP workspace for a generic install. The public homepage is never the fallback.
Registry introspection proxy
Registries that require a local stdio process can run the included credential-free
proxy. It forwards MCP JSON-RPC traffic to the same verified remote endpoint; it
does not mock or reimplement any 2ools tools. It translates the stdio handshake
into the remote endpoint's current per-request MCP envelope and returns the live
schemas from 2ools.
The included Dockerfile runs the same dependency-free proxy for reproducible
registry introspection. It intentionally does not perform an interactive OAuth
flow. Clients using authenticated workspace tools should connect directly to
https://2ools.app/mcp so OAuth remains end-to-end with 2ools.
2ools Skill
For assistants that support repository skills, add or copy the
2ools Skill. It keeps the temporary-preview and
OAuth workspace boundaries explicit. Client support for remote MCP and Skill
folders varies; the live start page routes each client to its supported flow.
Try it with no account
Ask your assistant:
> Write this as one standalone HTML document, create a free 2ools preview, and show me the link.
You get back a real URL that anyone can open. It expires after 24 hours.
---
What you can do with it
| Ask your assistant… | It uses |
|---|---|
| "Open this generated site in 2ools and give me a client-safe preview link" | create_public_preview |
| "Save this conversation as a durable 2ools project" | build_from_conversation |
| "Make the hours bigger and show me the new version" | refine_project |
| "Compare the last two versions" | compare_versions |
| "What changed on this project since Tuesday?" | get_project_activity |
| "Export the source as a zip" | prepare_version_export |