Sensorist MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.0.1Updated Nov 7, 2026

Read gateways, sensor measurements and alarm history in Sensorist.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Hosted, read-only MCP server that lets an assistant read Sensorist gateways, sensor measurements and alarm history from your account.

What you can do
  • Read account and user details, including the full user hierarchy
  • List gateways with their sensors and data source ids
  • Fetch measurements for one gateway: latest, min/max, climate days, grouped ranges or raw pages
  • List alarms and their current state with recent log entries
  • Read alarm history, as time-ordered entries, in/out pairs or combined with system notifications
  • Check monthly tool-call usage, request a feature, or manage a Pro subscription
When to use it
Useful when you want to ask natural-language questions about your own Sensorist sensor network, such as which sensors exceeded a temperature threshold, the latest humidity per gateway, or when a cellar alarm triggered this month.
Requirements
Remote endpoint only, no local install; connect with the MCP URL. Sign-in is via OAuth, and the login page asks for the e-mail address and password of your Sensorist account (the one used at my.sensorist.com), which the server validates and stores per user. No API key or Authorization header goes in the client config. Free plan allows 50 tool calls per month.
Before you install
You hand your Sensorist account e-mail and password to the hosted service, which stores them per user, so trust in the operator matters. The data tools are read-only, but meta tools can start a paid Stripe subscription (Pro or Pro+), cancel it, or send a feature request; cancellation runs to the end of the paid period with no refund for the current period. Usage is metered, so heavy use hits the free limit or the Pro fair-use cap.

Installation

In SourceWeft

  1. Open Sensorist MCP by usefulapi in the dashboard and add it to a workspace.
  2. 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/io.usefulapi%2Fsensorist/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.

{
  "mcpServers": {
    "sensorist-by-usefulapi": {
      "type": "http",
      "url": "https://sensorist.usefulapi.io/mcp"
    }
  }
}

README

Sensorist MCP by usefulapi

Use your Sensorist account from Claude, Cursor, or any MCP client. Read gateways, sensor measurements and alarm history, read-only. Hosted, no local install: connect with your own credentials.

Live endpoint: https://sensorist.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://sensorist.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http sensorist https://sensorist.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "sensorist": {      "url": "https://sensorist.usefulapi.io/mcp"    }  }}

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Sensorist credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/sensorist/

On first connect you provide the e-mail address and password of your Sensorist login (the one you use at my.sensorist.com). The server validates it and stores it per user. No keys go in config files.

Tools

ToolTypeWhat it does
sensorist_get_userreadGet the account
sensorist_list_gatewaysreadList gateways
sensorist_get_measurementsreadGet measurements
sensorist_list_alarmsreadList alarms
sensorist_list_alarm_historyreadList alarm history
sensorist_usage_statusmetaUsage status (free-tier meter)
sensorist_request_featuremetaRequest a missing feature
sensorist_upgrademetaUpgrade to Pro or Pro+
sensorist_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)Unlimited*

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with sensorist_upgrade (it returns a Stripe Checkout link). Cancel any time with sensorist_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running sensorist_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

Source: servers/sensorist/README.md at commit 2450437

Tools

5

sensorist_get_user

Get the account

Get the user and account details of the signed-in Sensorist login. With list=true, return every user in the account hierarchy. Sensorist API: GET /v1/users.

Parameterslist

sensorist_list_gateways

List gateways

List the gateways (device inventory) of the account. Each gateway lists its sensors, and each sensor its data sources (the ids the measurement tool needs). By default only master gateways are returned. Sensorist API: GET /v1/gateways.

Parametersfromserialsinclude_slaves

sensorist_get_measurements

Get measurements

Get sensor measurements for data sources of ONE gateway. type: latest (most recent values), min_max (minimum and maximum with dates), climate (ETCCDI climate days), range (grouped average, minimum and maximum) or raw (unfiltered, up to 5,000 per page; pass the reply's next value as offset to read on). The default period is the past week. Sensorist API: GET /v1/measurements.

Parameterstofromtyperequiredticksoffsetseq_toindicesintervalseq_fromdata_sourcesrequired

sensorist_list_alarms

List alarms

List the data source alarms set by the account and their current state, with the most recent log entries. Sensorist API: GET /v1/alarms.

Parametersinclude_notes

sensorist_list_alarm_history

List alarm history

Get the alarm log history: when each alarm went into and out of alarm. By default the entries are in time order. format=pairs returns each in/out pair together; format=combined adds system notifications. Sensorist API: GET /v1/alarms/history.

Parameterstofromalarmsformatinclude_notes

Version history

1
  1. v1.0.1LatestNov 7, 2026

Score

100% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations