# Estimote MCP MCP > Estimote MCP manages your entire beacon fleet and physical space data via natural conversation. Use this to list devices, monitor real-time sensor readings like temperature or light levels, track visitor flow counts in specific zones, and organize multiple store locations from a single AI agent connection. ## Overview - **Category:** cloud-infrastructure - **Price:** Free - **Tags:** bluetooth-beacons, proximity-analytics, sensor-telemetry, fleet-management, smart-buildings, location-tracking ## Description Connect your Estimote Cloud account to any AI client to take control of your beacon data workflows. Instead of jumping between the web dashboard and separate analytics tools, you talk to your agent about what's happening on the floor. You can get an immediate inventory of every deployed device, check its current battery level, or pull live environmental readings like ambient light and temperature. Need to know if visitor counts dipped last Tuesday? Ask for proximity metrics over a specific time range. This MCP lets you manage everything from device setup to high-level foot traffic reports using only natural language prompts. You'll find this tool integrated right here in the Vinkius catalog, making it simple to add physical asset intelligence directly into your workflow. ## Tools ### assign_tag_to_beacon Organizes a device by adding an organizational tag for easier grouping in analytics or campaigns. ### create_physical_location Registers a new site, like a store or office building, and assigns beacons to it for organized tracking. ### remove_beacon_device Permanently removes a beacon device from the cloud account when it is decommissioned or retired. ### get_device_analytics Generates aggregated metrics showing visitor detection counts and dwell times over a set period. ### get_beacon_details Retrieves the full current configuration and status of one specific beacon device for diagnostics. ### get_beacon_telemetry Pulls live environmental sensor data, such as temperature or ambient light, from a single beacon. ### list_beacon_devices Provides an inventory of all active beacon devices, listing their hardware type and current battery levels. ### list_physical_locations Retrieves a list of all registered physical sites, showing their names and coordinates. ### list_fleet_tags Lists every organizational tag currently defined in your cloud account for device categorization. ### update_beacon_settings Modifies a beacon's operating parameters, like transmission power or advertising intervals. ## Prompt Examples **Prompt:** ``` List all my beacons and their current battery status ``` **Response:** ``` Retrieving beacon fleet... I found 10 devices. Highlights: 'Entrance Beacon' (90%), 'Aisle 4' (15% - Low Battery), and 'Checkout' (100%). Would you like me to flag all devices with less than 20% battery? ``` **Prompt:** ``` What is the current temperature at 'Beacon-XYZ'? ``` **Response:** ``` Checking telemetry for Beacon-XYZ... The current temperature is 22.5°C (72.5°F). Ambient light is at 150 lux and no motion has been detected in the last 5 minutes. ``` **Prompt:** ``` Show me visitor analytics for the 'Main Store' tag from last month ``` **Response:** ``` Retrieving analytics for 'Main Store'... Last month, there were approximately 1,200 unique visitors with an average dwell time of 15 minutes. Detection frequency peaked on Saturdays between 2 PM and 4 PM. ``` ## Capabilities ### Inventory all beacons Get a complete list of every beacon device deployed, including its type and current battery status. ### Monitor live sensors Pull real-time environmental data like temperature or light levels from supported hardware. ### Analyze visitor flow Calculate aggregated metrics, such as unique visitor estimates and average time spent in a zone, over specific date ranges. ### Organize physical sites Register new venues or buildings, assigning beacons to a formal geographic location for organized tracking. ### Update device settings Change broadcasting parameters—like transmission power or advertising intervals—for specific beacon devices. ## Use Cases ### Diagnosing poor retail performance The manager noticed sales dropped after a floor layout change. They ask the agent to run `get_device_analytics` for the 'Seasonal Display' tag from last month, immediately showing that visitor detection counts plummeted in that specific zone. ### Auditing facility assets The engineer needs to know if a new wing is properly tracked. They first use `list_physical_locations` to find the building ID, then use `create_physical_location` to register it and assign all necessary beacons. ### Checking sensor health The facility team suspects a heating unit failure. They run `get_beacon_telemetry` on a nearby beacon, getting immediate confirmation of the dangerously low temperature reading. ### Decommissioning old hardware An outdated display area is being removed. The tech uses `remove_beacon_device` to permanently take the unit off the cloud roster before physically taking it down, ensuring clean records. ## Benefits - You can instantly check the battery status of all beacons by running `list_beacon_devices`, letting you prioritize maintenance before a critical failure occurs. - Need to know what's going on right now? Use `get_beacon_telemetry` to pull live data like temperature and light levels from a specific beacon, which is crucial for HVAC checks. - Instead of manually calculating traffic patterns, running `get_device_analytics` gives you visitor estimates and dwell time distributions over any date range in seconds. - Managing multiple sites? Use `create_physical_location` to register new stores or buildings, keeping all related beacons organized under one umbrella for analytics grouping. - If a beacon is misbehaving or needs a setting change, running `get_beacon_details` gives you the full shadow status so you know exactly what parameters need updating via `update_beacon_settings`. ## How It Works The bottom line is you get real-world location and sensor data presented in plain text by your AI agent. 1. You subscribe to this MCP and provide your Estimote App Token, linking the cloud account to your AI client. 2. Your agent uses the token to connect directly to the Estimote API endpoint. 3. The client executes tool calls based on your natural language request, retrieves the data, and presents a summarized answer. ## Frequently Asked Questions **How do I check if my beacon fleet is fully inventoried using list_beacon_devices?** Running `list_beacon_devices` gives you a complete, paginated record of all registered beacons. This report includes the MAC address, hardware type (Proximity/Location/Sticker), and current battery levels for an immediate inventory check. **Can I get temperature readings using get_beacon_telemetry?** Yes, `get_beacon_telemetry` pulls the most recent sensor data. If your beacon hardware supports it, you'll receive real-time readings for temperature, ambient light levels, and barometric pressure. **What is the difference between list_physical_locations and assign_tag_to_beacon?** `list_physical_locations` defines *where* the beacons are (the building or store). `assign_tag_to_beacon` organizes them by a logical group, like 'Holiday Campaign' or 'Second Floor,' regardless of where they physically sit. **How do I update the power settings for my beacons?** Use `update_beacon_settings`. You specify the beacon ID and the new parameters you want to change, like transmission power (dBm) or advertising interval (ms), which queues changes in the cloud shadow. **I need visitor counts for a specific zone. Which tool should I use? get_device_analytics?** That's right. `get_device_analytics` is designed to pull proximity data, giving you unique visitor estimates and dwell time distributions over the date range you specify. **If I use `remove_beacon_device`, does it stop the beacon from broadcasting entirely?** No, the physical broadcast continues. This tool permanently removes management control of the device from your Estimote Cloud account, but the hardware keeps running and broadcasting signals for legacy systems. **When I use `list_fleet_tags`, am I seeing tags that are already assigned to devices?** You see all defined organizational labels available in your cloud. These tags persist independently of the physical beacon and serve as logical groupings for filtering, allowing you to target specific segments across your entire fleet. **What is the required workflow after I use `create_physical_location`?** After creating a location record, you must assign your actual beacon devices to it. This step links the physical hardware assets to the newly defined site coordinates, allowing for accurate, location-scoped analytics. **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 do I update the advertising interval of a beacon via chat?** Use the 'update_beacon_settings' tool. Provide the beacon identifier and a JSON object with the new settings (e.g., '{"settings": {"advertisingInterval": 300}}'). The changes are queued in the cloud shadow and synced automatically. **Can I see real-time temperature data from my beacons through the agent?** Absolutely. Use the 'get_beacon_telemetry' tool. Your agent will fetch the most recent sensor readings, including temperature, light, and motion detection, directly from the beacon's cloud record.