
2ools
app.2oolsv0.3.1Updated Sep 30, 2026
Build, version, review, and export websites, web apps, and games from a conversation.
Installation
In SourceWeft
- Open 2ools in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://2ools.app/mcp"
}
}
}README
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.
[MCP Registry] [Transport] [Tools]
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
Tools
43 tools, each with explicit readOnlyHint and destructiveHint annotations so a
client can reason about blast radius before calling anything.
Free — no account required
Build and refine
Read a project
Review and approval
Feedback and shared notes
Export and sharing
Artifacts
Agents
Work assignments
Authentication
The authorization server publishes RFC 8414 and RFC 9728 discovery documents at
/.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource,
supports RFC 7591 dynamic client registration, rotates refresh tokens with family
revocation on replay, and stores only token digests.
Review authority is deliberately separate from build authority. projects:build
lets an agent produce candidate versions; approve_version and reject_version
require projects:approve, which is excluded from default grants. An agent that can
build cannot sign off on its own work unless a human explicitly delegates that.
Design notes
Source never travels through the model transcript. Exports and artifact downloads are five-minute signed URLs bound to the action, the account and the exact version. The MCP response carries metadata and links, not bytes — so a large site does not consume the context window, and generated source is not replayed into a provider log.
Shared previews run in an opaque-origin sandbox. A shared page is served under a
CSP sandbox with connect-src 'none', so a site built by a model cannot read the
viewer's cookies, storage, or reach the network.
External agent output enters review, not production. An artifact uploaded by an outside agent is stored immutably and marked pending; it cannot become the current version until a human with review authority approves that exact digest.
Interactive previews use MCP Apps. render_project_preview returns a real
interactive card via ui://2ools/project-preview-v1.html rather than a wall of text.
Links
- Product — https://2ools.app
- Connection guide — https://2ools.app/connect-ai
- Free website audit (28 deterministic checks, no account) — https://2ools.app/website-audit
- Benchmarks: 36 real sites scored — https://2ools.app/website-audit/benchmarks
- What 2ools does — https://2ools.app/product
- Pricing — https://2ools.app/pricing
- LLM guide — https://2ools.app/llms.txt
- Privacy & terms — https://2ools.app/legal
Registry
Published to the official Model Context Protocol registry under the
domain-verified namespace app.2ools/mcp.
Status
The endpoint is live in production. Health, including the exact deployed release:
License
MIT — see LICENSE. This repository holds the server's public manifest and documentation; the 2ools application itself is a hosted product.
Source: README.md at commit 477a235
Tools
0Version history
1- v0.3.1LatestSep 16, 2026

