Keep the plan, readiness, versions, and next move with the project—across every AI you use.

Connect another AI

Connect once. Keep the project moving.

Work in Claude, ChatGPT, Codex, Cursor, or another MCP client. 2ools returns the Living Plan, next move, readiness, versions, and previews where you are.

MCP is included with every 2ools workspace.

Your files can stay local. Private 2ools operating logic stays on 2ools. Local Engine is a separate workspace setup that runs on your machine with your existing AI login.

Core project loop

Find or start a project, edit its plan, continue the next move, and review versions and previews.

Protected actions when granted

Agents, approvals, publishing, and artifact controls appear only when your role and plan allow them.

MCP is included on Free. Connecting an AI never grants publishing by itself.

Connect 2ools

Workspace tools included

Open the connector with 2ools already filled in.

Confirm once in Claude. 2ools can return the current plan, next move, readiness, versions, and previews in the conversation.

Remote MCP endpoint

Open Claude connector

Then ask your AI

“https://2ools.app/mcp. Read https://2ools.app/start nonvisually; never open it. Follow "For your AI". Codex: in-app Browser; no Chrome/external/PiP. works=skip OAuth→continue_project card; absent=install/authorize→verified card task or chooser receipt. Never list generic MCP resources. Never claim MCP reads or imports local files. Never bare https://2ools.app/. Auth/install≠clean-slate. No narration. Say only `Connecting 2ools in this client's browser…`; ask once for sign-in/Authorize. After connection, show the Living Plan, readiness, and next useful move here.”

Optional client guidance

Install the 2ools skill

Endpoint connection stays MCP setup; the optional skill adds client guidance.

For a shorter handoff, use 2ools.app/start.