Energy Machines · MCP / REST
Use the Energy Machines catalogue from an AI agent
Our public MCP server gives AI assistants read-only access to the same published catalogue as this website: products, specifications, datasheets and installation cases. No account or API key is needed.
1. Tell your agent to use it
Paste this into your agent's instructions or the start of a conversation:
Use the Energy Machines public MCP server at https://heatpumps.energymachines.com/mcp (Streamable HTTP, no authentication) for anything about Energy Machines industrial heat pumps. Start by reading the catalogue_overview resource to learn the valid locales, units and filters. Then use search_products, get_product and compare_products, and cite the canonical product and datasheet URLs you used. Treat nominal ratings and individual temperature limits as screening data, not a confirmed operating point, and say clearly what is unknown. Never submit anything: when I want to inquire, use how_to_inquire to prepare a draft for me to review and send myself.If your agent cannot add MCP servers but can make web requests, give it the REST API instead: https://heatpumps.energymachines.com/api/public/v1 (OpenAPI description: https://heatpumps.energymachines.com/api/public/v1/openapi.json).
2. Add the server to your client
Server URL: https://heatpumps.energymachines.com/mcp. Transport: Streamable HTTP. Authentication: none.
https://heatpumps.energymachines.com/mcpClaude Code
claude mcp add --transport http energy-machines https://heatpumps.energymachines.com/mcpClaude apps: Settings → Connectors → Add custom connector, then paste the server URL.
Clients configured with an mcpServers JSON file
{
"mcpServers": {
"energy-machines": {
"url": "https://heatpumps.energymachines.com/mcp"
}
}
}Other clients may call this a remote MCP server or a custom connector. Choose HTTP / Streamable HTTP and no authentication.
3. Things to ask
We have 30 °C waste water from a process cooling loop and need about 1.5 MW of heat at 60 °C. Which Energy Machines heat pumps could fit? Explain your assumptions.Compare the specifications of the two best candidates side by side and link their datasheets.Find installation cases similar to a district-heating project and summarise them.Draft an inquiry about the selected heat pump for me to review. Do not send it.What the server offers
Tools
list_ | List public families containing published products. Use their stable slugs in the family filter. |
search_ | Search published products. Numeric filters use canonical kW and degrees C. Follow next_offset; confirm design-point performance with the manufacturer. |
get_ | Read a published product, flexible specifications, public media and documents. Missing values are unknown, never zero. |
compare_ | Compare the union of specification keys across published products; missing values are null. |
list_ | List public documents linked to published products; never the asset library or internal paths. |
get_ | Resolve a document still linked to a published product. Does not download its contents. |
list_ | List published installation case studies with canonical URLs and public product reference text. |
get_ | Read a published installation case, public media and converted flexible specifications. |
get_ | Read only known public company, technology, history and contact sections. |
how_ | Explain human-reviewed inquiry preparation. No drafts, email sending or submissions are performed. |
Prompts
select_ | Builds a shortlist from public catalogue evidence, asking for missing duty and temperature conditions. |
draft_ | Drafts an inquiry for a selected product, for human review. Never submits. |
Resources
energymachines:/ | Start here: locales, measurement systems, units, families and valid filter tokens. |
energymachines:/ | Published product families. |
energymachines:/ | A full published product. |
Languages, units, limits
The catalogue is inquiry-led: there are no prices, orders or write operations. Agents can prepare an inquiry draft; a person submits it from the product page or contacts the engineering team.
All operations accept locale and measurement_system codes configured by the catalogue. Omit them for site defaults. Missing translations use the public page fallback; the returned locale identifies the actual translation. Numeric search filters always use kW and degrees C. Lists accept offset and limit (default 25); follow next_offset until null. Compare slugs use a comma-separated list. The OpenAPI document describes every parameter and response.
REST and MCP share a process-local quota: by default 120 requests per client and 3,000 globally per 60 seconds. Operators may configure these limits. HTTP 429 includes Retry-After in seconds. REST supports ETag / If-None-Match and public caching for 60 seconds (shared caches: 300 seconds). MCP is no-store. REST allows any browser origin for GET; MCP permits the site and approved assistant origins. Tool name and outcome are counted in anonymous daily aggregates; arguments and IPs are never included in those aggregates.
REST API
The REST API returns the same data as the MCP tools. Each MCP tool has a GET endpoint under https://heatpumps.energymachines.com/api/public/v1.
REST API reference · OpenAPI 3.1 description
Example requests
curl 'https://heatpumps.energymachines.com/api/public/v1/products?limit=2'
curl 'https://heatpumps.energymachines.com/api/public/v1/products?min_heating_capacity_kw=1000&min_supply_temp_c=60&min_source_temp_c=30'
curl 'https://heatpumps.energymachines.com/api/public/v1/families'
curl 'https://heatpumps.energymachines.com/api/public/v1/cases?limit=2'Terms of use
Use public catalogue data for engineering discovery and cite the canonical product and document URLs. Respect caching and Retry-After. Availability and specifications may change. Confirm duty, source/supply temperatures, fluids and simultaneous operating conditions with Energy Machines before design or procurement. This service offers no performance guarantee.