2,500+ MCP servers ready to use
Vinkius

Honeywell Forge MCP Server for Vercel AI SDK 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 Tools SDK

The Vercel AI SDK is the TypeScript toolkit for building AI-powered applications. Connect Honeywell Forge through Vinkius and every tool is available as a typed function. ready for React Server Components, API routes, or any Node.js backend.

Vinkius supports streamable HTTP and SSE.

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";

async function main() {
  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      // Your Vinkius token. get it at cloud.vinkius.com
      url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    },
  });

  try {
    const tools = await mcpClient.tools();
    const { text } = await generateText({
      model: openai("gpt-4o"),
      tools,
      prompt: "Using Honeywell Forge, list all available capabilities.",
    });
    console.log(text);
  } finally {
    await mcpClient.close();
  }
}

main();
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 Vercel AI SDK via MCP

Follow these steps to integrate the Honeywell Forge MCP Server with Vercel AI SDK.

01

Install dependencies

Run npm install @ai-sdk/mcp ai @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the script

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

The SDK discovers 11 tools from Honeywell Forge and passes them to the LLM

Why Use Vercel AI SDK with the Honeywell Forge MCP Server

Vercel AI SDK provides unique advantages when paired with Honeywell Forge through the Model Context Protocol.

01

TypeScript-first: every MCP tool gets full type inference, IDE autocomplete, and compile-time error checking out of the box

02

Framework-agnostic core works with Next.js, Nuxt, SvelteKit, or any Node.js runtime. same Honeywell Forge integration everywhere

03

Built-in streaming UI primitives let you display Honeywell Forge tool results progressively in React, Svelte, or Vue components

04

Edge-compatible: the AI SDK runs on Vercel Edge Functions, Cloudflare Workers, and other edge runtimes for minimal latency

Honeywell Forge + Vercel AI SDK Use Cases

Practical scenarios where Vercel AI SDK combined with the Honeywell Forge MCP Server delivers measurable value.

01

AI-powered web apps: build dashboards that query Honeywell Forge in real-time and stream results to the UI with zero loading states

02

API backends: create serverless endpoints that orchestrate Honeywell Forge tools and return structured JSON responses to any frontend

03

Chatbots with tool use: embed Honeywell Forge capabilities into conversational interfaces with streaming responses and tool call visibility

04

Internal tools: build admin panels where team members interact with Honeywell Forge through natural language queries

Honeywell Forge MCP Tools for Vercel AI SDK (11)

These 11 tools become available when you connect Honeywell Forge to Vercel AI SDK 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 Vercel AI SDK

Common issues when connecting Honeywell Forge to Vercel AI SDK through the Vinkius, and how to resolve them.

01

createMCPClient is not a function

Install: npm install @ai-sdk/mcp

Honeywell Forge + Vercel AI SDK FAQ

Common questions about integrating Honeywell Forge MCP Server with Vercel AI SDK.

01

How does the Vercel AI SDK connect to MCP servers?

Import createMCPClient from @ai-sdk/mcp and pass the server URL. The SDK discovers all tools and provides typed TypeScript interfaces for each one.
02

Can I use MCP tools in Edge Functions?

Yes. The AI SDK is fully edge-compatible. MCP connections work on Vercel Edge Functions, Cloudflare Workers, and similar runtimes.
03

Does it support streaming tool results?

Yes. The SDK provides streaming primitives like useChat and streamText that handle tool calls and display results progressively in the UI.

Connect Honeywell Forge to Vercel AI SDK

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