Torque360 MCP Server
Related Servers
Alternatives to Torque360 MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceConnects AI agents to a signed-in AutoRepair Cloud account through a hosted Cloud Browser, enabling repair quotes, parts and workflow tracking, workshop bookings, technician hours, daily sales and customer vehicle history, with customer-facing actions held for approval.7Elastic 2.0

Actionbookofficial
AlicenseNot gradedqualityCmaintenanceConnects AI agents to a real Chrome browser through a hosted MCP endpoint, enabling them to search action manuals and operate logged-in websites via direct API calls or UI automation.1,632Apache 2.0- AlicenseBqualityBmaintenanceEnables AI agents to browse, click, type and read on any website the user is logged in to, using encrypted local sessions with multiple named accounts per site. It behaves like a human, asks for confirmation before risky actions, and hands control back for CAPTCHAs or 2FA.2860 PyPIMIT
- AlicenseAqualityBmaintenanceEnables AI agents to safely read pages, click, fill forms, upload files, navigate tabs, and take token-efficient screenshots in an already logged-in browser session through one shared local connection.10MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to automate a user-owned local Chrome browser or personal Linux host by opening pages, reading controls, clicking, filling forms, extracting information, taking screenshots, and saving encrypted profiles, while pausing for brief human handoff during logins, CAPTCHAs, 2FA, or OAuth approval.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and terminal users to control a logged-in Chrome browser, performing actions like opening pages, searching, filling forms, and taking screenshots without re-authentication.MIT
TDQS
Scored across 7 tools
The core interaction tools (read, click, type) target clearly different actions on numbered page elements, and open/close bracket the session lifecycle distinctly. The only mild overlap is between guide (instructions) and status (account/connection readiness), which an agent could occasionally conflate when troubleshooting.
Every tool follows the same predictable torque360_<verb> pattern (read, click, type, close, guide, status, open), with no camelCase mixing or alternate verb styles. The shared prefix also makes the server's scope immediately obvious.
Seven tools is well-scoped for a browser-automation wrapper: each tool maps to one necessary capability (orient, open, read, click, type, check, close). Nothing feels redundant or missing at the count level.
The surface covers the full session lifecycle: status check, guide, open, read, click, type, and close, so core workflows on shop reports and pricing are achievable. Minor gaps exist for navigation (back/scroll), waiting for page loads, or verifying post-action state, but agents can work around these with repeated read calls.