Integrate Estimote with Claude, Cursor, Chatbots & AI Agents MCP Server

Q: Can my agent check the battery levels of all my beacons?

Yes. Use the 'listbeacondevices' tool. The agent retrieves the overarching inventory of your fleet, returning hardware types and precise battery levels for every registered device natively.

Manage beacon fleets via Estimote — list and configure devices, track proximity analytics, monitor sensor telemetry, and manage physical locations directly from any AI agent.

GDPR Free for Subscribers

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

assign

Assign tag to beacon on Estimote

If the tag does not exist, it is created automatically. A device can have multiple tags. Use to organize beacons by floor, zone, store section, or campaign. Tags persist in the cloud and do not require physical beacon access. Assign an organizational tag to a specific Estimote beacon device, adding it to a logical group for fleet management, analytics filtering, and proximity campaign targeting

create

Create physical location on Estimote

After creating a location, assign beacon devices to it for organized fleet management and location-scoped analytics. Use when deploying beacons at a new site. Register a new physical location (store, office, venue) in Estimote Cloud, providing the site name, street address, and geographic coordinates for beacon fleet organization and analytics grouping

get

Get beacon details on Estimote

The identifier is the beacon MAC address or Estimote Cloud ID. Returns the full device shadow including pending settings changes. Use to diagnose beacon configuration issues or verify firmware update status. Retrieve detailed configuration and status for a specific Estimote beacon device, including its current broadcasting power, advertising interval, sensor readings, firmware version, and physical location assignment

get

Get beacon telemetry on Estimote

Returns the most recent sensor readings from the beacon. Not all sensors are available on all hardware models. Estimote Proximity Beacons support temperature and motion; Location Beacons add light and pressure sensors. Use for environmental monitoring and occupancy detection. Retrieve real-time sensor telemetry data from a specific Estimote beacon, including temperature readings, ambient light levels, accelerometer motion detection, magnetometer orientation, and barometric pressure where supported by hardware

get

Get device analytics on Estimote

Supports query parameters for date range (from, to), device identifier, and tag filtering. Returns aggregated metrics showing how many mobile devices detected each beacon. Use for foot traffic analysis, retail engagement measurement, and space utilization studies. Retrieve proximity analytics data for Estimote beacon devices, including detection counts, unique visitor estimates, dwell time distributions, and engagement metrics over a specified time period

list

List beacon devices on Estimote

estimote.com. Returns a paginated array of beacon objects. Each beacon includes its MAC address (the most reliable identifier), iBeacon UUID/Major/Minor, Eddystone namespace/instance, and shadow settings. Use to inventory your deployed beacon fleet. List all Estimote beacon devices registered in your Estimote Cloud account, returning device identifiers, hardware types (Proximity/Location/Sticker), battery levels, firmware versions, and current configuration status

list

List fleet tags on Estimote

Returns an array of tag objects with names and associated device counts. Tags are the primary organizational mechanism in Estimote Cloud. Use to understand your current fleet taxonomy before assigning or filtering devices. List all organizational tags defined in your Estimote Cloud account, which are used to group and categorize beacon devices by location, use case, department, or any custom classification scheme

list

List physical locations on Estimote

Returns an array of location objects. Locations serve as containers for organizing beacons by physical site. Each location can have multiple beacon devices assigned to it. Use to audit your deployment footprint across multiple sites. List all physical locations (venues/buildings/stores) registered in your Estimote Cloud account, returning location names, addresses, geographic coordinates, and the number of beacons deployed at each site

remove

Remove beacon device on Estimote

WARNING: This permanently removes the device from your fleet. The beacon will continue broadcasting but will no longer be managed by Estimote Cloud. Only use when decommissioning hardware. The device can be re-added later via the Estimote app. Permanently remove an Estimote beacon device from your Cloud account, deleting all associated configuration, analytics history, and location assignments. This action is irreversible

update

Update beacon settings on Estimote

Changes are queued in the cloud shadow and synchronized to the physical beacon when a device running the Estimote SDK connects to it. Common updates include name, tags, broadcasting power (dBm), and advertising interval (ms). Update the configuration of a specific Estimote beacon device by modifying its broadcasting parameters, advertising interval, transmission power, or attached metadata tags through the Estimote Cloud shadow system

Security & Code Integrity Audit

Every tool in the Estimote MCP Server is continuously audited by the Vinkius Security Engine. We guarantee zero-trust payload isolation, strict data boundaries, and deterministic execution for enterprise-grade AI agents.

A+Score: 100

How Vinkius protects your data

Can I audit what my AI agents are doing with this integration?

Yes, Vinkius provides an immutable, HMAC-chained audit log. Every tool execution, payload, and response is tracked in real-time on your dashboard, giving you complete visibility into your agent's actions.

What happens if the underlying API rate limits my agent?

Our edge infrastructure automatically handles backoffs, queueing, and throttling. If an AI agent sends too many erratic requests, Vinkius manages the rate limits gracefully, ensuring your backend doesn't crash.

How does the AI access my passwords and credentials?

It simply doesn't. On Vinkius, your passwords, API keys, and login details are kept in a secure vault. The AI (like ChatGPT or Claude) merely "asks" Vinkius to perform the task. Vinkius opens the door, does the work, and hands the result back to the AI. Your credentials are never seen, read, or learned by the artificial intelligence.

Can my agent check the battery levels of all my beacons?

Yes. Use the 'list_beacon_devices' tool. The agent retrieves the overarching inventory of your fleet, returning hardware types and precise battery levels for every registered device natively.

How Chatbots Interact with Estimote

Build automated workflows with Cursor and Claude Code by connecting to the Estimote MCP server.

Claude Code Integration for bluetooth beacons

The Estimote integration allows Cursor and ChatGPT to securely fetch bluetooth beacons data. It handles the API requests required for cloud infrastructure operations.

Scaling proximity analytics via MCP

The Estimote MCP integration translates natural language prompts into structured proximity analytics queries. This allows agents to fetch and update cloud infrastructure records securely.