2ools MCP Server
OfficialRelated Servers
Alternatives to 2ools MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for the OffByOne website factory, enabling agents to generate, validate, and manage full-stack web projects through safe, deterministic tools.-
- AlicenseNot gradedqualityFmaintenanceLocal stdio MCP server for working on Intern-hosted sites through guarded Git checkouts. It enables authentication, site preparation, testing, validation, and publishing via coding harnesses like Codex and Claude Code.43 npmMIT
- AlicenseAqualityAmaintenanceOutbound-only remote shell, detached long-running jobs, and temporary file courier for AI agents. Hosted Streamable HTTP plus stdio via npx -y @aicommander/mcp.11MIT
- AlicenseBqualityDmaintenanceProduction-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.1528 npm3MIT
- FlicenseBqualityAmaintenanceChatGPT-compatible MCP server and Electron launcher for controlled local project-file access, providing read-only and approval-gated write tools over STDIO or HTTP with optional OAuth and HTTPS tunneling.19-
- AlicenseNot gradedqualityDmaintenanceA minimal WebSocket-based MCP server implementation that enables modern tool integrations with VSCode, Claude, and other applications.6 npmISC
TDQS
Scored across 43 tools
Most tools have clearly distinct resource targets (project, build, version, artifact, agent, activity, feedback, work assignment). A few pairs like get_project and get_project_context could be confused, but descriptions clarify the differences.
Tool names consistently use snake_case verb-first patterns (get_, list_, create_, add_, remove_, approve_, reject_, cancel_, prepare_). Minor variation between create_ and add_ for similar actions, but overall the pattern is predictable.
43 tools is far beyond the typical well-scoped range. Even for a broad platform, this volume is overwhelming and likely makes it harder for agents to select the right tool. Many tools could be consolidated or grouped.
The tool surface covers the main lifecycle: project creation, building, versioning, sharing, artifacts, approvals, feedback, agents, activity, and work assignments. Minor gaps like lack of explicit delete/archive operations, which may be intentional given the immutable nature of versions and artifacts.