Integration

smart-me integration

smart-me is a Swiss cloud energy-management platform for its electricity, water, gas and heat meters, pico EV charging stations and M-BUS gateways. Read devices and their live or historical values (power, counter readings per tariff, voltage, current), push values for custom devices, switch outputs and run device actions, read and set device configuration, manage folders, sub users, virtual meters and virtual tariffs, control pico charging stations (live charging data, history, settings, cable lock, load management currents), manage M-BUS gateways and their meters, and register Realtime API webhooks. OAuth application and refresh-token management, NFC card access tokens, account deletion and the portal's folder menu editing are not exposed, and stored passwords and device keys are left out of every answer. Authentication is a smart-me API key created in the web portal (API, Api Keys), sent as Authorization: ApiKey <key>; historical value series need a Professional licence.

Connect smart-me How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in smart-me.Built from the 63 smart-me tools below, on the connection you add once.

What you can do with smart-me

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Device, 4 operations

get_deviceGet deviceGETReturns one device with its latest values: active power per phase, counter readings per tariff, import and export, voltage, current and power factor per phase, temperature, flow rate, switch states, digital and analog inputs and outputs.
list_devicesList devicesGETLists every device (meter, charging station, gateway, custom device) of the account with its latest values: active power per phase, counter readings per tariff, import and export, voltage, current and power factor per phase, temperature, flow rate.
set_device_switchSet device switchPUTTurns a switch of a device on or off (switchNumber picks the phase switch on multi-switch meters). For new uses the vendor recommends set_device_actions.
upsert_deviceUpsert devicePOSTCreates a device or writes values to an existing one.

Meter, 4 operations

create_mbus_meterCreate mbus meterPOSTAdds an M-BUS meter definition to a gateway, by primary or secondary address, with its baud rate.
delete_mbus_meterDelete mbus meterDELETEDeletes one M-BUS meter definition from a gateway. The meter in smart-me is not deleted.
get_mbus_meterGet mbus meterGETReturns one M-BUS meter of a gateway by its position: smart-me meter id, name, addressing, baud rate, state and energy type.
update_mbus_meterUpdate mbus meterPUTUpdates an M-BUS meter definition on a gateway (addressing mode, addresses, baud rate, reset commands).

Setting, 4 operations

delete_folderDelete folderDELETEDeletes a folder, identified by its id.
get_folder_settingsGet folder settingsGETReturns the settings of a folder or meter: name, description, type, serial number, enabled flag, value corrections, parent folder and visualization.
get_pico_settingsGet pico settingsGETReturns the settings of a pico charging station: name, serial number, authentication type, display brightness, current limits, idle image, load management group, Modbus TCP, enabled flag, car id detection, cable lock, internal IP and DNS name.
save_folder_settingsSave folder settingsPOSTAdds a folder or edits a folder or meter: name, description, folder type, serial number, enabled flag, value corrections, parent folder and visualization. Use an empty id to add a new folder.

Assign, 3 operations

assign_folderAssign folderPOSTMoves a folder or meter (source) under another folder (target), which is how a folder structure is built.
assign_user_to_folderAssign user to folderPOSTAssigns a user (by id) to a folder; oldFolder is the folder the user is moved from.
unassign_user_from_folderUnassign user from folderDELETERemoves a user's assignment to a folder.

Custom device, 3 operations

get_custom_deviceGet custom deviceGETReturns one custom device with its id, name, serial, latest values and value date.
list_custom_devicesList custom devicesGETLists the account's custom devices (non-meter devices that push their own measurement values) with their id, name, serial, values and value date.
upsert_custom_deviceUpsert custom devicePOSTCreates a custom device (any non-meter device that adds measurement values to the smart-me cloud) or writes values to an existing one. Leave id empty to create; send an existing id with values to record them at valueDate or server time.

Mbus, 3 operations

delete_mbus_gatewayDelete mbus gatewayDELETEDeletes an M-BUS gateway. The meters connected to it are not deleted.
get_mbus_gatewayGet mbus gatewayGETReturns an M-BUS gateway with its name, serial number, last contact, readout interval, state and all connected M-BUS meters.
update_mbus_gatewayUpdate mbus gatewayPUTChanges the name, readout interval and whether new meters may be added on an M-BUS gateway.

Register for realtime api, 3 operations

create_realtime_api_registrationCreate realtime api registrationPOSTRegisters an endpoint URL with the Realtime API, which then receives the data of one meter or of all the account's devices as soon as it reaches the cloud (sent as protobuf). Optional basic-auth username and password protect your endpoint.
delete_realtime_api_registrationDelete realtime api registrationDELETEDeletes a Realtime API registration.
list_realtime_api_registrationsList realtime api registrationsGETLists the account's Realtime API registrations (webhooks that receive device data as soon as it reaches the cloud): id, registration type, meter id or serial and endpoint URL and username.

Sub user, 3 operations

delete_sub_userDelete sub userDELETEDeletes a sub user of the calling user.
get_sub_userGet sub userGETReturns one sub user assigned to the calling user: id, username, email, permission level and access start and end dates.
upsert_sub_userUpsert sub userPOSTCreates or updates a sub user: username, email, permission level, access start and end dates and optionally a new password. Leave id empty to create one.

Action, 2 operations

list_device_actionsList device actionsGETLists the actions a device supports (switches, analog outputs and so on), each with its name, OBIS code (used as the action id), type and allowed value range. Pass them to set_device_actions.
set_device_actionsSet device actionsPOSTExecutes actions on a device, for example switching a relay or setting an analog output, by OBIS code and value as listed by list_device_actions.

Loadmanagementgroup, 2 operations

get_load_management_groupGet load management groupGETReturns one pico load management group: name, maximum fuse current, connection-lost behaviour, phase switching settings and number of stations.
list_load_management_groupsList load management groupsGETLists the account's pico load management groups, each with id, name, maximum fuse current, connection-lost behaviour, phase switching settings and number of stations.

Meter folder information, 2 operations

get_meter_folder_informationGet meter folder informationGETBeta. Returns general information about a meter or folder: name, whether it is a folder, its available inputs and outputs, and hardware and firmware versions.
rename_meter_or_folderRename meter or folderPOSTSets the name of a meter or folder.

Smart me device configuration, 2 operations

get_device_configurationGet device configurationGETReturns the configuration of a smart-me device: upload interval, phase switch, output and input configuration, reactive energy display, Modbus TCP and DNS update state.
set_device_configurationSet device configurationPOSTChanges the configuration of a smart-me device (upload interval, switch, output and input configuration, reactive energy, Modbus TCP, DNS update, PIN code or encryption key of an external meter). The device must be online.

Virtual tariff, 2 operations

get_folder_virtual_tariffsGet folder virtual tariffsGETReturns the virtual tariffs of one folder with the folder name and date.
list_virtual_tariffsList virtual tariffsGETLists the virtual tariffs of every folder of the user, each folder with its id, name, date and tariffs.

Additional device information, 1 operation

get_additional_device_informationGet additional device informationGETReturns technical details of a device: hardware and firmware version, an additional meter serial number, how it connects to the network and the connection signal strength.

Charging, 1 operation

get_pico_chargingGet pico chargingGETReturns the live charging data of a pico station: state, charging power and energy, duration, currents per phase, current limits, load management group, connection and signal, last warning or error and when it was last seen.

Current, 1 operation

set_load_management_currentSet load management currentPOSTSets the dynamic current, in mA, of the load management group a pico station belongs to (or of the single station), addressed by any station serial in the group.

Deleteallmeter, 1 operation

delete_all_mbus_metersDelete all mbus metersDELETEDeletes all M-BUS meters of a gateway. The gateway itself is not deleted.

Device by serial, 1 operation

get_device_by_serialGet device by serialGETReturns one device found by its serial number (the part of the meter's serial before the dash) with its latest values.

Devices by energy, 1 operation

list_devices_by_energy_typeList devices by energy typeGETLists the account's devices of one energy type (electricity, water, gas, heat, temperature, gateways, custom or virtual meters) with their latest values.

Devices by sub type, 1 operation

list_devices_by_sub_typeList devices by sub typeGETLists the account's devices of one sub type (for example charging stations or cold and hot water meters) with their latest values.

Fast send device value, 1 operation

trigger_fast_send_device_valuesTrigger fast send device valuesGETAsks a device to send its data every second for about 30 seconds, if it supports it. Returns no data; read the values with get_device_values. Not meant to be repeated to keep a device in fast mode.

Folder, 1 operation

get_folder_valuesGet folder valuesGETReturns the aggregated values of a folder or a meter: electricity counter and power, heat counter and power, water and gas counters and flow rates.

Folder menu, 1 operation

get_folder_menuGet folder menuGETReturns the account's folder tree (folders, meters and users) with each item's id, name, description, type, children and meter serial number. Use it to find folder ids.

History, 1 operation

get_pico_charging_historyGet pico charging historyGETReturns the recent charging sessions of a pico station, each with start time, duration, energy used and why it stopped.

Meter value, 1 operation

get_meter_values_at_dateGet meter values at dateGETReturns the counter readings of a meter at a given date (the last value recorded before it): total, per tariff, import and export.

Pico, 1 operation

list_pico_stationsList pico stationsGETLists the account's pico charging stations with their latest values.

Search, 1 operation

search_mbus_metersSearch mbus metersPOSTStarts a search for M-BUS meters connected to the gateway; read the results with get_mbus_gateway.

Threephasecurrent, 1 operation

set_load_management_three_phase_currentSet load management three phase currentPOSTSets the dynamic current of each phase (L1, L2, L3), in mA, for a pico load management group. Each value is 0 or between 6000 and 6400000, in multiples of 1000.

Tryenablecablelock, 1 operation

lock_pico_cableLock pico cablePOSTTries to lock the charging cable of a pico station. The station must be online with a cable connected and no car, otherwise it fails.

User, 1 operation

get_userGet userGETReturns the user the credentials belong to: id, username, email, whether it is an admin, its permissions and the sub users it created.

Value, 1 operation

get_device_valuesGet device valuesGETReturns the latest values of a device as a list of OBIS code and value pairs, with the value date.

Values in past, 1 operation

get_device_values_at_dateGet device values at dateGETReturns the values of a device at a given date (the last value recorded before it) as OBIS code and value pairs.

Values in past multiple, 1 operation

get_device_values_historyGet device values historyGETReturns a series of values of a device between two dates, at most 1000 per call, each as OBIS code and value pairs with its date. Needs a smart-me Professional licence.

Values in past multiple interpolated, 1 operation

get_device_values_interpolatedGet device values interpolatedGETReturns values of a device between two dates interpolated to a fixed grid of 15 minutes or 1 day, with the interpolation quality and whether the series is complete. Needs a smart-me Professional licence.

Virtual billing meter deactivate, 1 operation

deactivate_virtual_meterDeactivate virtual meterPOSTBeta. Deactivates a virtual billing meter.

Virtual meter calculate formula, 1 operation

calculate_virtual_meterCalculate virtual meterGETCalculates a virtual meter from a formula over other meters and returns it as a device with values. A meter is written ID("<meter id>") and combined with + - * / and parentheses.

Virtual tariff consumption, 1 operation

get_virtual_tariff_consumptionGet virtual tariff consumptionGETReturns the consumption of a folder split by its virtual tariffs between two dates (UTC).

Virtual tariffs for property, 1 operation

list_property_virtual_tariffsList property virtual tariffsGETLists the virtual tariffs of a property (a folder).

Visualizationtype, 1 operation

list_visualization_typesList visualization typesGETLists the visualizations a folder can use, each with its type number, name, description and the folder or meter slots it expects.

Use smart-me from Claude Code, Cursor or Codex

Connect smart-me in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its smart-me operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect smart-me

Create your workspace
Sign up free. Nothing to install.
Connect smart-me once
Add your smart-me connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.