Skip to main content
Glama
HERO Software MCP server

HERO Software MCP server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key. Required for execution; discovery works without a key.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

HERO Software through Cotlet.dev. Call hero_software_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
hero_software_guideA

How to work in HERO Software (trade business projects, quotes, invoices and appointments): its screens and the sign-in link. Call this first.

hero_software_statusA

Check that your Cotlet.dev account and HERO Software are ready: account, credits and HERO Software connection.

hero_software_openA

Open a HERO Software page in your signed-in Cloud Browser (default https://login.hero-software.de) to work with trade business projects, quotes, invoices and appointments.

hero_software_readA

Read the current HERO Software page: its text and numbered buttons, links and fields.

hero_software_clickB

Click a numbered element on the current HERO Software page.

hero_software_typeC

Type text into a numbered field on the current HERO Software page.

hero_software_closeA

Close the HERO Software browser session when the work is done, so credits stop running.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

Seven tools is well-scoped for a browser-automation workflow, with each tool earning its place. No redundant or filler tools are present.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues