An astronaut overseeing a futuristic data hub

Connect Johnson Controls Metasys to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Bring your building automation data directly into your AI agent.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 8 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 8 available through Metasys.

  1. 01

    Get object

    This capability retrieves a specific Metasys object. It provides attributes, present values, status, and links to child objects or alarms using a UUID.

  2. 02

    List objects

    This capability returns a list of Metasys objects. It provides names, descriptions, and types for devices, points, and equipment nodes in the BACnet-style tree.

  3. 03

    Get object children

    This capability lists the children of a specific Metasys object. Use it to navigate down the building hierarchy through paginated results.

  4. 04

    List alarms

    This capability pulls a list of Metasys alarms. It covers fire, security, and HVAC alarms across the entire site.

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through Metasys.

  1. 05

    Get alarm annotations

    This capability fetches operator notes and annotations tied to a specific alarm.

  2. 06

    List equipment

    This capability lists physical equipment groups like chillers, AHUs, and RTUs within the Metasys site.

  3. 07

    List network devices

    This capability provides a view of the network topology. It lists controllers and field buses along with their firmware versions.

  4. 08

    List spaces

    This capability lists the rooms, zones, and floors in the building. It includes links to temperature and humidity data for comfort monitoring.

Real work

What teams actually run

01

Rapid Alarm Response

An agent monitors the alarm list and alerts the team when a critical HVAC failure occurs.

02

Comfort Monitoring

The AI checks room-level temperature and humidity data to ensure tenant comfort.

03

Equipment Health Checks

An agent pulls present values from chillers and AHUs to identify performance drifts.

04

Network Auditing

A technician uses the agent to quickly list all controllers and their current firmware versions.

One connector, every AI

Metasys works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Metasys to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

923ms average. Fast in production.

Metasys is checked daily against the live service.

Daily averagePeak 1081ms
Oct 3Today
Fastest day
740ms
Slowest day
1081ms
14-day trend
Slowing+8%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 8 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Metasys, so you can see the experience inside your AI.

It does not authenticate your account with Metasys. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Metasys Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_FyqXvuPn1K8lpLjWN4kixqSYoydH28zP26gj6ykz/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Metasys capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "johnson-controls-metasys-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_FyqXvuPn1K8lpLjWN4kixqSYoydH28zP26gj6ykz/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Metasys in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Metasys owners hand off.

This MCP is designed for professionals managing large-scale building automation systems who need to bridge physical hardware with intelligent software.

  • 01

    Building Operations Teams

    They hand off routine monitoring and alarm triage to their AI agent.

  • 02

    Energy Managers

    They use the agent to pull data for fault detection and efficiency analysis.

  • 03

    Systems Integrators

    They use the capability to verify network device status and firmware versions.

FAQ

Questions Metasys owners ask.

  • 01

    What version of Metasys is required?

    You need a Metasys Site running version 11 or higher with the REST API enabled.

  • 02

    How does the MCP handle authentication?

    The MCP uses the official REST API v4 method, logging in via POST to receive a Bearer JWT access token. It handles token refreshes automatically every 60 minutes.

  • 03

    What kind of credentials do I need?

    You must use an account with an Access Type set to API. For Active Directory accounts, use the format name@domain.

  • 04

    Can my AI agent see operator notes?

    Yes, the MCP includes a capability to retrieve specific operator annotations for any alarm.

  • 05

    Which AI clients can I use with this?

    You can use this MCP with any compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 06

    What do I need on my Metasys site for this to work?

    A Metasys Site (ADS/OTI server) running Metasys v11+ with the REST API enabled, and an account whose Access Type is set to 'API' (created in the Metasys UI). Active Directory users format the username as name@domain.

  • 07

    Does the token expire?

    Yes. JWT expiry follows the Metasys profile. The official guidance is to refresh before 60 minutes; this MCP refreshes the token at 55 minutes automatically, so long monitoring sessions keep working.

Connect Metasys to Claude, Cursor, ChatGPT & more