Honeywell Forge MCP Server for Google ADK 11 tools — connect in under 2 minutes
Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Honeywell Forge as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
StreamableHTTPConnectionParams,
)
# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
connection_params=StreamableHTTPConnectionParams(
url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
)
)
agent = Agent(
model="gemini-2.5-pro",
name="honeywell_forge_agent",
instruction=(
"You help users interact with Honeywell Forge "
"using 11 available tools."
),
tools=[mcp_tools],
)
* 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 Google ADK via MCP
Follow these steps to integrate the Honeywell Forge MCP Server with Google ADK.
Install Google ADK
Run pip install google-adk
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Create the agent
Save the code above and integrate into your ADK workflow
Explore tools
The agent will discover 11 tools from Honeywell Forge via MCP
Why Use Google ADK with the Honeywell Forge MCP Server
Google ADK provides unique advantages when paired with Honeywell Forge through the Model Context Protocol.
Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution
Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Honeywell Forge
Production-ready features like session management, evaluation, and deployment come built-in. not bolted on
Seamless integration with Google Cloud services means you can combine Honeywell Forge tools with BigQuery, Vertex AI, and Cloud Functions
Honeywell Forge + Google ADK Use Cases
Practical scenarios where Google ADK combined with the Honeywell Forge MCP Server delivers measurable value.
Enterprise data agents: ADK agents query Honeywell Forge and cross-reference results with internal databases for comprehensive analysis
Multi-modal workflows: combine Honeywell Forge tool responses with Gemini's vision and language capabilities in a single agent
Automated compliance checks: schedule ADK agents to query Honeywell Forge regularly and flag policy violations or configuration drift
Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Honeywell Forge
Honeywell Forge MCP Tools for Google ADK (11)
These 11 tools become available when you connect Honeywell Forge to Google ADK via MCP:
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
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
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
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
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
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
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
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
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
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
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 Google ADK
Common issues when connecting Honeywell Forge to Google ADK through the Vinkius, and how to resolve them.
McpToolset not found
pip install --upgrade google-adkHoneywell Forge + Google ADK FAQ
Common questions about integrating Honeywell Forge MCP Server with Google ADK.
How does Google ADK connect to MCP servers?
Can ADK agents use multiple MCP servers?
Which Gemini models work best with MCP tools?
Connect Honeywell Forge with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Honeywell Forge to Google ADK
Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.