2ools MCP Server is 2ools' remote MCP server for building, versioning, reviewing, and exporting websites, web apps, and games within the AI chat client users already use. Its core idea: the assistant writes the site, and 2ools makes the result persist—every result becomes a recoverable version, previews are shareable links that open without an account, and source code is exported as ordinary files with no dependence on a proprietary runtime.
Main capabilities
- 43 tools in total, each with explicit readOnlyHint and destructiveHint annotations, making it easy for clients to judge the scope of impact before calling.
- Free and no account required: create_public_preview can turn a standalone HTML document the model has just written into a real viewable URL that anyone can open, expiring after 24 hours.
- Feature groups such as build and optimize, review and approve, feedback and shared notes, export and share, and work assignment.
- render_project_preview returns a real interactive card (based on MCP Apps) via ui://2ools/project-preview-v1.html, rather than a long block of text.
How to use
- Paste the connection prompt into the AI client you want to connect; the MCP endpoint is https://2ools.app/mcp。
- Apart from the free tools, the remaining tools connect through OAuth 2.1 with PKCE and least-privilege scopes.
- The live start page https://2ools.app/start is the current connection flow for all clients: it detects the current client path, keeps OAuth active, and leaves logging in and clicking "Authorize" to the user themselves.
- Manual MCP configuration applies only to clients that cannot manage remote MCP settings on their own, as a fallback.
- Registry introspection proxy: registries that require a local stdio process can run the included credential-free proxy, which forwards MCP JSON-RPC traffic to the same verified remote endpoint; it does not emulate or reimplement any 2ools tool, but instead translates the stdio handshake into the remote endpoint's current per-request MCP envelope and returns 2ools' live schema. The included Dockerfile can run the same dependency-free proxy for reproducible registry introspection, and intentionally does not perform the interactive OAuth flow. Clients using authenticated workspace tools should connect directly to https://2ools.app/mcp，以便 OAuth end-to-end and 2ools stay connected.
- Assistants that support repository skills can add or copy the 2ools Skill, which explicitly maintains ephemeral preview and OAuth workspace boundaries. Client support for remote MCP and Skill folders varies, and the live onboarding page routes each client to the flow it supports.
- No-account trial: you can ask the assistant to "write this as a standalone HTML document, create a free 2ools preview, then give me the link." This yields a real URL that anyone can open, expiring after 24 hours.
Use cases
- Build websites, web apps, and games in AI chat where you need version management, preview sharing, and source export.
- Collaborative or approval workflows that need build and review permissions separated.
- Need shareable but safe previews so model-built pages cannot read the viewer's cookies, storage, or access the network.
- Artifacts produced by external agents need human review before entering production.
Limitations and security design
- Review permission and build permission are deliberately separated: projects:build allows an agent to generate candidate versions; approve_version and reject_version require projects:approve, which is not included in the default authorization. An agent that can build cannot sign off on its own work unless a human explicitly authorizes it.
- Source code never passes through the model conversation record: exports and artifact downloads are signed URLs valid for five minutes, bound to the action, account, and exact version. MCP responses carry only metadata and links, not bytes, so large sites do not consume the context window, and generated source code is not replayed into provider logs.
- Shared previews run in an opaque-origin sandbox: shared pages are served under a CSP sandbox with connect-src 'none' set, so model-built sites cannot read the viewer's cookies, storage, or access the network.
- External agent output goes to review rather than production: artifacts uploaded by external agents are stored immutably and marked as pending review, and cannot become the current version unless a human with review permission approves that exact digest.
- 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.
Additional information
- Product address:https://2ools.app
- Connection guide:https://2ools.app/connect-ai
- Free website audit (28 deterministic checks, no account required):https://2ools.app/website-audit
- Benchmarks (36 real site scores):https://2ools.app/website-audit/benchmarks
- Feature introduction:https://2ools.app/product
- Pricing:https://2ools.app/pricing
- LLM guide:https://2ools.app/llms.txt
- Privacy and terms:https://2ools.app/legal
- Published to the official Model Context Protocol registry, with the domain-verified namespace app.2ools/mcp
- The endpoint is already running in production; health checks include the exact deployed version
- License: MIT, see LICENSE for details; this repository holds the server's public manifest and documentation, and the 2ools app itself is a hosted product
