Maci

energy.maciPublished by maci.energyOfficial publisherv1.0.0Updated Nov 7, 2026

Read refrigeration units, service history, F-gas logs and alarms in Maci. Read only.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Read-only MCP access to Maci refrigeration data: sites, units, service history, F-gas leak checks and alarms, answered in plain language.

What you can do
  • List sites and refrigeration units, filtered by site, status or recent changes
  • Read a unit's passport, nameplate, refrigerant, charge, CO2 equivalent and components
  • Read service history entries for a unit
  • Check F-gas leak check status and the F-gas log (requires Maci Service)
  • List and open alarms, including who took them and how they were closed
  • Check this month's API call usage against the limit
When to use it
Useful for refrigeration or facilities teams already on Maci who want an assistant to answer questions about leak check schedules, open alarms, service history and refrigerant data without navigating the app.
Requirements
Remote Streamable HTTP endpoint at mcp.maci.energy; no local package. OAuth 2.1 login with a passkey, choosing the organisation; only an organisation admin can connect it. Some tools need the Maci Service subscription.
Before you install
Read-only, but every tool call counts as an API call against a monthly limit. Data read is sent to the assistant and its provider, so only connect an assistant your organisation permits. Connections are listed under Konto → API-nøgler and expire after 30 days of inactivity.

Installation

In SourceWeft

  1. Open Maci in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/energy.maci%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "maci": {
      "type": "http",
      "url": "https://mcp.maci.energy/mcp"
    }
  }
}

README

Maci for AI assistants (MCP)

Connect Maci to an assistant that speaks the Model Context Protocol and ask about your refrigeration units in your own words:

  • Which of our units are due a leak check in November?
  • Are there open alarms at the Vesterbro store, and has anyone taken them?
  • When was MC-0482 last serviced, and what was done?
https://mcp.maci.energy/mcp

The server is read only. It reads through Maci's API, so the assistant sees what your organisation may see in Maci and nothing more, and every tool call counts as an API call. The full guide is at api.maci.energy/docs/ai-assistants.

Connect

Claude (claude.ai and the desktop app): Settings → Connectors → Add custom connector. Name it Maci, paste the address above and choose Connect.

ChatGPT: Settings → Connectors, add a custom connector with the address above. (ChatGPT may ask you to turn on developer mode for custom connectors.)

Claude Code:

sh
claude mcp add --transport http maci https://mcp.maci.energy/mcp

Then run /mcp in Claude Code and choose Maci to log in.

Cursor, VS Code and others: see clients.md.

In each case the assistant sends you to Maci. Log in as always, choose the organisation and say yes with your passkey. Only an organisation's admin can connect it.

Tools

ToolWhat it givesScope
list_sitesThe organisation's sites, and customers' sites it has units on through a grantunits:read
list_unitsThe units it works with, filtered by site, status or what changed since a timeunits:read
get_unitOne unit's passport: master data, nameplate, refrigerant, charge, CO2 equivalent, componentsunits:read
list_componentsA unit's componentsunits:read
list_service_entriesA unit's service historyservice:read
get_fgas_statusA unit's leak check status: interval, last check, next due (needs Maci Service)fgas:read
list_fgas_entriesA unit's F-log (needs Maci Service)fgas:read
list_alarmsAlarms from Maci Intelligence, filtered by open, unit or since a timealarms:read
get_alarmOne alarm with its values, who took it and how it was closedalarms:read
get_usageThis month's calls and the limitany

Lists come in pages of up to 100; the assistant follows next_cursor by itself.

Skills

Instructions that walk the assistant through a task, step by step. Give one to the assistant (in Claude: add it as a skill, or paste it into the conversation) and ask for the task.

SkillWhat it does
Leak check planThe units due a leak check in a period, by site, with the overdue ones first
F-gas overviewRefrigerant, charge and CO2 equivalent by site, and the units without a leak check status
Alarm reportA period's alarms: how many, how fast they were taken, how many were false
Before a visitWhat a technician should know before going to a unit

More examples of questions: prompts.md.

Your data

The assistant reads only, and only what your organisation may see. What it reads goes to the assistant you chose and its provider, so connect only an assistant your organisation is allowed to use. Each connection is listed in the app under Konto → API-nøgler, "Forbundne AI-assistenter", with who made it and when it was last used. Removing it stops it at once, and a connection that is not used for 30 days ends by itself.

For developers

The server follows the MCP specification of 2026-07-28: Streamable HTTP, OAuth 2.1 with PKCE (S256), Client ID Metadata Documents and dynamic client registration, with app.maci.energy as the authorization server. Details in the guide.

Source: mcp/README.md at commit 4bc1696

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 31, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.