List alerts and data loggers, count active alerts, and acknowledge alerts in DicksonOne. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the DicksonOne connector, then ask in plain words. The AI picks the tools.
For food safety and facility teams that watch fridges, rooms and storage with DicksonOne loggers.
List the active alerts, filtered by location or severity. Read the locations to find the ids to filter by, and count the alerts by severity.
List the alerts and pick one. Then read the comments that users added to that alert, with author and time.
List the data loggers on the account, optionally with archived or replaced ones. Use a logger token to filter the alerts of that logger.
Read the alert and its comments first. Then acknowledge it. An alert that is already acknowledged returns an error and nothing changes.
Changes dataThe login page asks for your DicksonOne API key.
Find it in DicksonOne → Manage → API Keys. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone. Your account needs an active subscription with API access.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"dicksonone": {
"url": "https://dicksonone.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"dicksonone": {
"type": "http",
"url": "https://dicksonone.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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: the login page asks for your DicksonOne API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this DicksonOne server only. Subscribe with dicksonone_upgrade (it returns a Stripe Checkout link). Cancel any time with dicksonone_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running dicksonone_upgrade before then undoes the cancel. Or write to [email protected].
dicksonone_whoamidicksonone_list_alertsdicksonone_get_alert_summarydicksonone_list_alert_commentsdicksonone_list_locationsdicksonone_list_devicesdicksonone_acknowledge_alertdicksonone_usage_statusdicksonone_request_featuredicksonone_upgradedicksonone_cancel_subscriptionReview active alerts by location and severity. Read the comments on an alert. Find a data logger and its alerts. Acknowledge an alert after you handle it. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by DicksonOne. The server calls the DicksonOne API with your own DicksonOne access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your DicksonOne API key. See Before you connect for where to find it.
No. 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: the login page asks for your DicksonOne API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the DicksonOne API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in DicksonOne.
Yes, if you approve it. 1 of the 7 DicksonOne tools can create or change data. The other 6 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this DicksonOne server only. Cancel any time: Pro then runs to the end of the paid period. Run dicksonone_usage_status to see how many calls you used.
Ask the AI to run dicksonone_upgrade: it returns a Stripe Checkout link. To cancel, run dicksonone_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with dicksonone_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.