2,500+ MCP servers ready to use
Vinkius

Honeywell Forge MCP Server for Claude Desktop 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Honeywell Forge and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "honeywell-forge": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Honeywell Forge
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Honeywell Forge MCP Server

Connect Honeywell Forge to any AI agent via MCP.

How to Connect Honeywell Forge to Claude Desktop via MCP

Follow these steps to integrate the Honeywell Forge MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using Honeywell Forge

Look for the 🔌 icon in the chat. your 11 tools are now available

Why Use Claude Desktop with the Honeywell Forge MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Honeywell Forge through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Honeywell Forge + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Honeywell Forge MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Honeywell Forge MCP Tools for Claude Desktop (11)

These 11 tools become available when you connect Honeywell Forge to Claude Desktop via MCP:

01

acknowledge_alarm

Acknowledgment does not resolve or clear the underlying condition—it simply records that a human has reviewed the alarm and is aware of it. This updates the alarm state from "unacknowledged" to "acknowledged" in the Forge audit log, which is important for compliance and incident-tracking workflows. Provide the exact alarm ID as returned by get_alarms. Use this during incident response to track which alarms have been seen by the operations team. Acknowledge an active alarm in Honeywell Forge

02

get_alarms

Alarms cover a wide range of conditions: security breaches (door forced, tailgating), fire and life safety (smoke detector activation, pull station), HVAC faults, and system health warnings. Each alarm record includes severity level, timestamp, source device, description, and acknowledgment status. Optionally filter by building_id to scope results to a single site. Use this to triage active incidents, audit historical events, or identify recurring fault patterns. List active and historical alarms across all buildings or a specific building

03

get_building_details

Returns comprehensive metadata including HVAC zones, floor plans, linked subsystems (access control, fire life safety, video surveillance), energy targets, and operating schedules. Use this when you need a deep-dive view of a single site before performing operations like checking alarms or querying energy usage. Get detailed information about a specific Honeywell Forge building

04

get_door_status

The response includes whether the door is currently open or closed, locked or unlocked, and any active fault conditions such as "door held open" or "forced open". This is a read-only, point-in-time snapshot—use it to verify the physical state of a door before granting access or investigating a security event. Get the real-time status of a specific door or access point

05

get_energy_usage

Returns aggregated consumption data including total kWh, cost estimates, demand peaks, and breakdowns by subsystem (HVAC, lighting, plug loads). Metrics may be presented as time-series data points with timestamps, allowing trend analysis and comparison against energy budgets. Use this to monitor sustainability KPIs, identify wasteful consumption patterns, or prepare energy audit reports for facility managers. Get energy consumption data for a specific building

06

get_temperature_data

Returns data points including zone temperature, setpoint targets, humidity levels, and HVAC equipment status (compressor running, valve position, fan speed). This data is essential for thermal comfort analysis, energy optimization, and proactive maintenance—such as identifying zones that consistently deviate from setpoints or detecting equipment degradation before failure. Use this to diagnose comfort complaints or validate HVAC scheduling changes. Get temperature and HVAC sensor data for a specific building

07

list_access_points

An access point represents a physical entry device—door, gate, turnstile, or barrier—managed by the Forge access control subsystem. Each record includes the access point ID, name, current lock state, door status (open/closed/forced), assigned access level, and the zone it belongs to. Use this to audit physical security surfaces before running lock/unlock commands or investigating door-forced alarm events. List all access control points (doors, gates, turnstiles) for a building

08

list_buildings

Each record contains the building identifier, name, address, operational status, and metadata such as time zone and total floor area. Use this tool as the entry point for any building-centric workflow—once you have the building ID you can drill down into access points, alarms, energy metrics, or video feeds. List all buildings registered in Honeywell Forge

09

list_video_feeds

Each record represents a camera or NVR channel with metadata including camera name, location within the building, stream URL (RTSP or HLS), resolution, current online/offline status, and recording mode (continuous, motion-triggered, scheduled). Use this to discover which cameras are available for live viewing or forensic review, and to map camera IDs to physical locations before correlating video with alarm events. List available video surveillance feeds for a building

10

lock_door

The door will immediately engage its locking mechanism and transition to a secured state. Only authorized credentials holders can override this lock via normal badge or PIN access. Use this when securing a building after hours, during a lockdown event, or to enforce temporary access restrictions. Confirm the door identity with list_access_points before executing. Lock a specific door or access point in Honeywell Forge

11

unlock_door

The door will disengage its lock and enter a free-access state until explicitly re-locked or returned to its scheduled access control mode. Use this for emergency egress, visitor accommodation, or maintenance access. Always verify the correct access point ID before unlocking to avoid unintended security gaps. Unlock a specific door or access point in Honeywell Forge

Troubleshooting Honeywell Forge MCP Server with Claude Desktop

Common issues when connecting Honeywell Forge to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Honeywell Forge + Claude Desktop FAQ

Common questions about integrating Honeywell Forge MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect Honeywell Forge to Claude Desktop

Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.