device_mgr_enterprise_getDevicesLABSCO SUMMARY
One connection instead of an integration per API against an IoT platform.
Rather than exposing every endpoint, it balances the surface down to a handful of tools per API, which keeps a platform this wide usable from a single agent session — and one Bearer token covers all of it.
What it is
A server that fronts the Acceleronix OpenAPIs, grouped by access tier, so device management and platform services are reachable as tools instead of REST calls.
What you get
- Device lifecycle and configuration through the enterprise device manager
- Device state read and written through the device shadow
- Device binding and user association for end-user accounts
- Weather, data storage, rule engine, OTA, Matter and family services among the covered APIs
- Three access tiers — EndUser, Enterprise and Open — behind one Bearer token
- A default set of APIs enabled on install; others — mail, SMS, push and work order among them — present but switched off
Requirements
A Bearer token, which is the single credential across every API the server exposes. It deploys to Cloudflare Workers.
Setup effort
Build from source — git clone https://github.com/Acceleronix/swagger-mcp-server.git
USE CASES
01
Checking on a device an enterprise customer reported
Pull the device record from the enterprise device manager and read its current configuration.
02
Pushing a state change to hardware in the field
Write to the device shadow and let the platform reconcile it with the device when it next connects.
03
Getting a new unit onto a customer's account
Bind the device to the end user so it shows up in their app.
04
Adding local conditions to a device reading
Fetch current weather for the device's location so a rule or a report has the context around the measurement.
5 tools
Listed in project docs. Your client may show a different list.
binding_enduser_bindDevicedeviceshadow_enterprise_updateShadowweather_enduser_getCurrentWeatherlist_apisBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- npx on PATH
- A Cloudflare account to deploy the Worker to (npm run deploy runs wrangler deploy)
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/Acceleronix/swagger-mcp-server.git
cd swagger-mcp-server
npm installUpdate the authentication tokens in src/config.ts: each API entry's auth: { type: 'bearer', token: '<YOUR_TOKEN>' } takes your Acceleronix Bearer token
TERMINAL
npm run deployMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"iot-apis": {
"command": "npx",
"args": [
"mcp-remote",
"https://swagger-mcp-server.<YOUR_ACCOUNT>.workers.dev/sse"
]
}
}
}<YOUR_ACCOUNT> is your own Cloudflare Workers subdomain — npm run deploy publishes the server at https://swagger-mcp-server.<YOUR_ACCOUNT>.workers.dev/sse, and the Bearer token travels with that deployment, so nothing else goes in this block.
