mocop
Browse · Docs · Guide · Analyze

2ools

MCP server by 2ools · mcp

2ools keeps AI-assisted projects understood, protected, and moving toward readiness across native AI workflows. It maintains source-free project continuity, versioned builds, attributable work, protected previews, and portable artifacts. Binary transfers use short-lived URLs so bytes never enter MCP model output. Private operating logic is never returned through MCP. First test an existing native 2ools tool. If it succeeds, this client is already authenticated: never start OAuth or ask the person to sign in. Only after a native call is rejected should the current client's native remote-MCP OAuth run with its callback or listener kept alive. Open that attempt's exact approval URL in this chat's embedded browser, ask once for sign-in or Authorize, and reuse that same pane after success. Never recommend the device flow, a user-visible terminal, or an external browser when an embedded browser exists. Once authenticated, call list_projects. The person's initiating intent wins over project…

Endpoint: https://2ools.app/mcp

Verification: observed. Source: crawl.

Capabilities (91)

  • create_public_preview
  • list_build_systems
  • list_connected_engines
  • get_project_engine_workspace
  • attach_project_engine_workspace
  • register_existing_project
  • build_from_conversation
  • start_project_on_engine
  • refine_project
  • get_build
  • get_engine_dispatch
  • compare_versions
  • list_approval_requests
  • approve_version
  • reject_version
  • cancel_build
  • get_account_profile
  • update_account_profile
  • get_project_access
  • invite_project_member
  • update_project_member_role
  • remove_project_member
  • revoke_project_invite
  • list_projects
  • get_project
About · Contact · Privacy