HERO Handwerk MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HERO_API_KEY | Yes | API key from HERO support (required). Gives access to your company data. | |
| HERO_BASE_URL | No | API host for the HERO API. | https://login.hero-software.de |
| HERO_TIMEOUT_MS | No | Request timeout in milliseconds. | 30000 |
| HERO_ALLOW_WRITES | No | Set to true to enable hero_create_lead, hero_add_logbook_entry and GraphQL mutations. Read-only by default. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hero_list_customersA | List contacts from HERO (customers by default). Use |
| hero_list_projectsA | List projects (HERO 'project matches') with project number, trade/measure, customer, site address and current status. Use |
| hero_get_projectA | Get full details for one or more projects by id: customer, contact person, site address, status, all documents (quotes, invoices, with PDF links) and the project logbook/history. |
| hero_list_documentsA | List customer documents (quotes/Angebote, invoices/Rechnungen, order confirmations, ...) with number, type, net value, VAT, status and PDF link. Use |
| hero_list_appointmentsA | List calendar events/appointments (Termine) from HERO. Fields are selected automatically from the HERO schema. Pass date filters via |
| hero_list_productsA | List products/articles from the HERO product catalogue (supply product versions), e.g. to look up prices or article numbers. Fields are selected automatically from the HERO schema. |
| hero_schemaA | Explore the HERO GraphQL schema. Without arguments: lists all available queries and mutations with their arguments. With |
| hero_graphqlA | Run a custom GraphQL query against HERO for anything the other tools don't cover. Read-only unless the server was started with HERO_ALLOW_WRITES=true. Use hero_schema to discover fields first. |
| hero_create_leadA | Create a new customer enquiry/project in HERO via the Lead API (e.g. from a phone call, email or website form). Requires customer email and ZIP code. HERO de-duplicates customers by email. Requires HERO_ALLOW_WRITES=true. Always confirm the details with the user before calling. |
| hero_add_logbook_entryA | Add an entry to a project's logbook in HERO (e.g. a call note or site-visit summary). The exact argument names come from the HERO schema: call hero_schema and look at the add_logbook_entry mutation first, then pass them in |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each list tool targets a clearly distinct resource (customers, projects, documents, appointments, products), and get_project/create_lead/add_logbook_entry are unambiguous. The only mild overlap is hero_graphql, which is a generic escape hatch that can replicate anything, but its description frames it as a fallback so boundaries stay clear.
All tools use the hero_ prefix with a consistent verb_noun pattern (list_customers, get_project, create_lead, add_logbook_entry). hero_schema and hero_graphql deviate slightly by being bare nouns rather than verb_noun, but remain readable and predictable.
Ten tools is well-scoped for an ERP/CRM integration covering listing, detail retrieval, write actions, and a schema/query escape hatch. Each tool earns its place without redundancy.
The surface covers listing across the core resources, project detail, schema discovery, and two write operations, which is strong for a read-oriented integration. Detail-by-id lookups for customers/products/documents and update/delete operations are absent, but hero_graphql provides a workaround for those gaps.