---
title: Explore in your own AI assistant
canonical: "https://www.frostlogic.se/platform/mcp/"
lastUpdated: 2026-11-14
twinOf: "https://www.frostlogic.se/platform/mcp/"
---
# Explore in your own AI assistant

Customers connect Claude, ChatGPT, VS Code, Cursor and other MCP-compatible assistants to FrostLogic Explore. Investigation, reporting and configuration from the tools you already use.

- Off by default
- OAuth
- Same approval as Explore AI

> Last updated: 2026-11-14. Twin of https://www.frostlogic.se/platform/mcp/.

## Explore, from the assistant you already open

- MCP (Model Context Protocol) is an open standard for connecting AI assistants to external tools and data. Explore exposes a customer MCP connection so your team can work the building from Claude Desktop, Claude Code, ChatGPT, VS Code, Cursor, or another MCP-compatible assistant.
- This is a product feature for Explore customers. New buyers book a meeting, see a demo, then start a free 90-day pilot.
- Setup is documented inside Explore.

## Investigation, reporting and configuration

- All the tools needed for a full building investigation, reporting and configuration are available through the MCP.
- The connection supports read and write. Writes only where you allow: write access is off by default, granted per scope. Proposals go through the same approval process as Explore's own AI.

- Full investigation, reporting and configuration surface through the assistant once connected.
- Reads the same building record operators already trust in Explore.
- Write access: off by default, granted per scope.
- Writes use the same approval process as Explore's own AI.

## Where customers connect today

Named assistants we support for customer MCP connections, plus other MCP-compatible clients your team already runs.

- Claude Desktop
- Claude Code
- ChatGPT
- VS Code
- Cursor
- Other MCP-compatible assistants

## Included, off by default, enabled on request

- MCP is included in both paid plans and the free pilot. See [pricing](/pricing/) for the plan sheet.
- The feature starts off. FrostLogic enables it per tenant when you ask. Tenant admins can keep it off so users do not share building data with personal assistants.
- Authentication is OAuth. The endpoint is private to customers. Using a personal assistant sends tenant data to that assistant's provider. That is why the default is off.

At a glance

How Explore MCP is packaged and gated for customers.

Plans

Included in both paid plans and the free pilot

Default

Off; enabled per tenant on request

Auth

OAuth

Writes

Off by default, granted per scope

Setup

Documented inside Explore

Next step

[Book a meeting](/contact-us/?interest=building_check)

## What operators ask once connected

Shape of useful asks after MCP is on. Results depend on your building data; these are prompts, not sample outputs.

### Overnight cold floor

Investigate why floor 3 ran cold overnight and rank the likely causes.

### Attention Queue brief

Summarise the highest-priority Attention Queue items for this building.

### Evidence pack

Draft an energy and compliance evidence pack for last quarter from the sensor record.

### Setpoint proposal

Propose an after-hours setpoint change for meeting rooms. Hold it for approval before anything writes.

## MCP questions from customers

### What is MCP on Explore?

MCP (Model Context Protocol) is an open standard for connecting AI assistants to external tools and data. On Explore it is the customer connection that lets your assistant work the same investigation, reporting and configuration surface operators already use in the product.

### Who is this for?

Explore customers. Your team connects the assistants you already use.

### Is it included in our plan?

Yes. MCP is included in both paid plans and the free pilot. Details live on [pricing](/pricing/).

### Why is it off by default?

Because using a personal assistant sends tenant data to that assistant's provider. FrostLogic enables MCP per tenant on request. Admins can keep it off.

### Can the assistant write setpoints?

Yes, only where you allow. Write access is off by default and granted per scope. Writes go through the same approval process as Explore's own AI.

### Where do we find setup steps?

Inside Explore. The endpoint is private to customers. Setup steps live in the product, not on this site.