HERO Software MCP server
Related Servers
Alternatives to HERO Software MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables ChatGPT, Claude and other AI agents to manage availability, blocked time, forms, invoices and client reports in a signed-in account, with write actions requiring approval by default. It connects through Cotlet.dev either as a hosted endpoint or as a local stdio server that forwards tool calls.7Elastic 2.0
- AlicenseAqualityBmaintenanceEnables ChatGPT, Claude, and other AI agents to manage appointments, customers, services, staff calendars, and notes in Setmore through natural language via Cotlet.dev.7Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceConnects AI agents to a signed-in contractor account through Cotlet.dev so they can work with estimates, leads, change orders, and job costs. Supports drafting line items, tracking estimate views, reading margins and recorded costs, and reviewing changes before writes are sent.Elastic 2.0
- AlicenseAqualityBmaintenanceConnects ChatGPT, Claude, Codex and Claude Code through Cotlet.dev to a signed-in construction management account, enabling work with projects, estimates, bids, change orders, daily logs, RFIs, invoices and related workflows. It exposes 31 read and write capabilities, most write actions requiring confirmation before anything is sent or changed.7Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to work with a signed-in Buildern contractor account through Cotlet.dev, including estimates, schedules, budgets, bills, client invoices, project to-dos, and site diaries, with review before write operations.Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to work inside a signed-in field-service account through Cotlet.dev — scheduling recurring jobs, finding customers, creating invoices and recording payments — with invoices, reminders and crew messages held for approval by default.Elastic 2.0
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: guide explains the system, status checks account readiness, and open/read/click/type/close form a non-overlapping browser-action sequence. There is no confusion about which tool to pick for a given step.
All tools share the consistent hero_software_ prefix followed by a concise verb (open, read, click, type, close) or clearly labeled noun (guide, status). The snake_case convention is uniform throughout.
Seven tools is well-scoped for a browser-automation workflow, with each tool earning its place. No redundant or filler tools are present.
The surface covers the full browser lifecycle (open, read, click, type, close) plus onboarding (guide) and health (status). Minor gaps like scroll or explicit navigation beyond open are not covered but most workflows can work around them.