2ools

What 2ools MCP server does

The 2ools MCP server lets an AI assistant create and manage websites, web apps, and games through the 2ools platform. A conversation can become a durable project and queued build, after which the assistant can create revised child versions from concrete feedback, inspect build progress, compare versions, and retrieve project context.

It also supports review and delivery workflows. Agents can read activity, collect page-anchored feedback, manage shared notes and links, approve or reject versions when delegated review authority is available, and make a selected version active. Saved versions can be previewed, shared through public or code-protected links, or exported as plain files without a proprietary runtime.

How it works

The remote endpoint is https://2ools.app/mcp and uses Streamable HTTP. Authenticated workspace tools connect through OAuth 2.1 with PKCE and least-privilege scopes. The live setup page at https://2ools.app/start provides the current connection procedure for the client being used; manual configuration is intended as a fallback for clients that cannot manage remote MCP setup.

One capability does not require authentication: create_public_preview accepts a complete standalone HTML document already produced in the conversation and returns a temporary, read-only preview URL. These previews expire after 24 hours. Authenticated operations work with projects, versions, review state, activity, sharing, and artifacts rather than returning source from comparison or project-preview reads.

The repository also includes a credential-free proxy for registries that require a local stdio process. Running npm ci followed by npm start starts the proxy, which forwards MCP JSON-RPC traffic to the remote service and exposes its live schemas. The proxy does not perform interactive OAuth; clients that need authenticated workspace tools should connect directly to the remote endpoint.

Setup and configuration

For normal use, connect the client to the remote MCP endpoint and follow the instructions at https://2ools.app/start. The setup flow keeps OAuth in the client’s supported in-app browser or preview pane. After authorization, the initiating context can open a known project, start a new or existing project flow, or use the authenticated MCP workspace.

The repository contains a Dockerfile for running the same registry-introspection proxy. No environment variables are specified in the provided material. A repository skill is also available for assistants that support skill folders; it documents the boundary between temporary previews and authenticated OAuth workspace operations.

Tools and capabilities

The 2ools MCP server exposes 43 tools grouped around these tasks:

• Build and refine projects, inspect build status, cancel eligible builds, compare saved versions, and list available Curators, Rulebooks, and Skills.
• List projects, read project details and source-free context, render saved-version previews, and inspect or wait for project activity.
• List approval requests, approve or reject versions, and manage attributable review feedback.
• Read, add, or remove shared project pins containing notes and safe HTTP(S) links.
• Create temporary export URLs, manage durable public or code-protected share links, and revoke them.
• List artifacts, inspect immutable version history and provenance, and prepare artifact upload or download URLs.

Tool annotations identify read-only and destructive behavior so compatible clients can assess the effect of a call before running it.

Limitations and notes

The free standalone preview accepts only a complete HTML document that has already been created in the conversation. It is temporary, read-only, and expires after 24 hours. Durable projects and the remaining workspace tools require authentication.

Export and artifact transfer URLs are temporary and last five minutes. Approval and feedback actions have role constraints: version approval or rejection requires separately delegated review authority, while resolving project feedback is owner-only. The registry proxy is intended for introspection and does not replace the direct authenticated connection.

The 2ools MCP server is a remote service, so client support for remote MCP, OAuth, in-app browser flows, and repository skills varies by client. The live start page is the authoritative setup path.