Golioth MCP for AI. Control your entire IoT hardware fleet from conversation.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
Golioth MCP connects your AI agent directly to your entire fleet of IoT hardware. You can list projects, register devices, and read real-time sensor data—all from a single conversation.
It gives you remote control over everything connected to the Golioth cloud without ever leaving your IDE or chat window.
What AI agents can do with Golioth Automation
Create project
Creates a new container project within the Golioth platform for grouping related devices.
Get lightdb state
Retrieves the current, real-time data state from a specified device using LightDB State.
List devices
Generates a list of all active hardware units assigned to an existing Golioth project.
Retrieve a full list of all available Golioth IoT projects.
Add, remove, or check the status of any hardware unit within a specified project.
Read real-time values from specific device paths (like temperature or power status) using LightDB State.
Write new configurations to a device, such as updating an LED color or setting a control threshold.
Ask an AI about this
Waiting for input…
What AI agents can do with Golioth: 7 Tools for IoT Management
These tools let you programmatically interact with every aspect of your Golioth cloud setup, from creating new projects to reading real-time sensor data.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Golioth on VinkiusCreate Project
Creates a new container project within the Golioth platform for grouping related devices.
Get Lightdb State
Retrieves the current, real-time data state from a specified device using LightDB...
List Devices
Generates a list of all active hardware units assigned to an existing Golioth...
List Projects
Provides a directory listing of every available Golioth project the user has access...
Register Device
Adds brand new hardware units into an existing project for fleet management.
Remove Device
Decommission a unit by removing it from its assigned Golioth project.
Set Lightdb State
Writes specific values to a device, allowing you to control settings like thresholds or power states.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Golioth, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Golioth. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 7 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The friction of managing hardware fleets is exhausting., Solved with Vinkius AI Gateway
Right now, controlling a fleet means context switching. You log into the web console to check if Project A exists. Then you open a separate tool to list all devices within it. To read sensor data, you have to jump yet again to a dashboard and manually query paths like 'temperature' or 'power.' It's a cycle of logins, clicks, and copy-pasting.
With this MCP, that process disappears. You talk to your agent, asking for the status of a specific device in a project. The agent runs the necessary checks—using tools like `list_devices` then `get_lightdb_state`—and gives you the answer immediately. It’s one conversation; all the complexity is hidden.
Golioth MCP: Control your hardware without logging in.
The manual steps that vanish include navigating project menus, manually submitting device IDs for listing, and running individual read/write API calls. You never have to remember the specific endpoint or data structure again.
It's not just reading data; it’s writing commands. Need to test a new threshold? Use `set_lightdb_state` through your agent. Your entire hardware ecosystem is now manageable from one single conversational point.
What your AI can actually do with this
Need to manage complex physical hardware? This MCP connects your AI agent directly to your Golioth IoT cloud, giving you full command over your entire connected device fleet. Instead of logging into a separate console and juggling multiple APIs, your agent acts like a universal remote terminal for all your projects.
Use it to list every project or check the status of specific sensors across dozens of devices. You can register new units as they come online, remove old ones, and even read and write real-time data paths—like changing an LED color or adjusting a sensor threshold—using natural conversation. When you connect through Vinkius, your AI client gains access to this entire catalog, meaning you don't have to switch context between different tools just to run diagnostics.
It makes monitoring device connectivity and managing credentials as simple as talking to your agent.
019ea5ef-bc73-716f-8fb5-1281e9b2a65c Here's how it actually works
The bottom line is that your natural language instructions trigger specific hardware actions without you ever seeing an API call.
Subscribe to this MCP on Vinkius and provide your unique Golioth API Key.
Your AI agent connects and authenticates with the IoT cloud platform.
You give a conversational command, like 'Check the temperature for Device X' or 'List all projects.' The agent executes the action and reports the data back.
Who is this actually for?
This MCP is for engineers who deal with physical, connected systems. If you spend your day checking sensor logs in a web console or writing manual scripts to test new firmware versions, this is what you need.
Debugging firmware requires checking live sensor values and device statuses instantly without leaving the chat interface.
Testing new hardware means registering and configuring devices directly from their IDE, skipping manual API calls.
Monitoring fleet deployment progress across multiple projects through simple conversational queries instead of complex dashboard filtering.
What Changes When You Connect
You eliminate context switching. Instead of jumping between the Golioth Console, a database interface, and your IDE, all device management happens through your agent.
Real-time control is instant. Use set_lightdb_state to change an LED color or adjust a sensor threshold without writing a single API script.
Manage growth effortlessly. You can use list_projects and then create_project to structure new deployments simply by asking your agent to do it.
Full lifecycle control is available. Need to onboard hardware? Use register_device. Finished with it? Run remove_device—all in one chat session.
Deep diagnostics are fast. If a sensor acts up, you use get_lightdb_state to pull the exact path data and status immediately.
See it in action
Debugging an intermittent fault
An IoT engineer notices that a remote temperature reading is spiking. They ask their agent, 'Show me the lightdb state for sensor X.' The agent uses get_lightdb_state and instantly returns the full history, allowing the engineer to pinpoint if the spike is hardware or software related.
Setting up a new deployment site
A product manager needs to deploy 50 sensors in a new building. They ask their agent to create_project for 'Building Alpha,' and then use list_devices repeatedly while running through the registration process with register_device until all hardware is accounted for.
Testing remote actuators
An embedded developer needs to test a relay switch. Instead of wiring up test code, they use their agent to call set_lightdb_state on the target device's 'actuator' path and immediately confirm that the command was received and executed.
Archiving old hardware
The team is retiring an entire sensor array. Rather than logging into the console to delete units, they ask their agent to list_devices first for verification, then use remove_device on the whole group in one go.
The honest tradeoffs
Manual API scripting
Writing a Python script that connects via HTTP, reads project names, loops through device IDs, and then executes separate read/write calls for every sensor.
You let your agent handle the boilerplate. Use list_projects first to identify the scope, then use targeted commands like get_lightdb_state or set_lightdb_state conversationally.
Switching between consoles
Opening tabs for the Golioth Web Console, a database query tool, and the device monitoring dashboard just to get one piece of information.
Your agent aggregates all this. You simply ask your client, 'What is the status of Device Y?' and it runs the necessary queries internally.
Using generic cloud tools
Relying on a general-purpose database connector that doesn't understand device paths or hardware states.
This MCP speaks Golioth. It understands concepts like 'LightDB State,' allowing you to use get_lightdb_state and set_lightdb_state precisely as intended.
When It Fits, When It Doesn't
Use this if your primary pain point is managing a diverse, physically distributed fleet of connected hardware. If you need the AI to act as a single pane of glass across project setup, device registration, and real-time data control, this MCP is perfect. Don't use it if you only need general database access; for that, look at a simple key-value store connector. Also, don't use it if your devices aren't running through the Golioth cloud infrastructure—you'll need an alternative platform connection.
Questions you might have
How do I start with the Golioth MCP? +
You subscribe to this MCP on Vinkius and provide your Golioth API Key. Once connected, you can immediately ask your agent to list_projects to see what infrastructure is already set up for you.
Can I use the Golioth MCP to change sensor values? +
Yes, you can control devices directly. Use the set_lightdb_state tool to write specific data paths, like changing an LED color or setting a new operational threshold for any connected unit.
What is the difference between list_devices and get_lightdb_state in Golioth MCP? +
Listing devices (list_devices) tells you which units exist in a project. Getting lightdb state (get_lightdb_state) tells you what specific data those existing units are reporting right now.
Does Golioth MCP support multi-project management? +
Absolutely. You can first use list_projects to see every project, and then switch contextually to run commands like register_device or get_lightdb_state in a different project.
If I decommission a unit, should I use remove_device? +
Yes. Use the remove_device tool when you need to formally take a unit offline and delete its record from the active Golioth project registry.
We've already built the connector for Golioth. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 7 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.