2,500+ MCP servers ready to use
Vinkius

Honeywell Process MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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 Process 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-process": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Honeywell Process
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 Process MCP Server

Connect Honeywell Process to any AI agent via MCP.

How to Connect Honeywell Process to VS Code Copilot via MCP

Follow these steps to integrate the Honeywell Process MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Honeywell Process

Ask Copilot: "Using Honeywell Process, help me...". 10 tools available

Why Use VS Code Copilot with the Honeywell Process MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Honeywell Process through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Honeywell Process + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Honeywell Process MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Honeywell Process MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Honeywell Process to VS Code Copilot via MCP:

01

create_maintenance_ticket

The ticket includes asset identification, problem description, priority level, requested completion date, and any relevant diagnostic data. Upon creation, the system assigns a work order number, routes the ticket to the appropriate maintenance team, and triggers notifications. Use this tool to formally log equipment issues, schedule preventive maintenance, or escalate asset health concerns to the maintenance workflow. Create a new maintenance work order or ticket for an asset

02

get_asset_details

Returns comprehensive information including hardware specifications, firmware version, network configuration, installation date, assigned location, maintenance history summary, and current operational parameters. Use this tool when you need in-depth information about a particular scanner, sensor, controller, or any other registered device in the Honeywell ecosystem. Get detailed information about a specific Honeywell asset or device

03

get_asset_health

Health data includes overall health score, component-level status, predicted remaining useful life, active fault codes, sensor readings, and recommended actions. Use this tool to quickly assess whether an asset requires immediate attention, verify post-maintenance recovery, or integrate health data into broader asset management workflows. Requires the specific asset identifier to retrieve targeted diagnostic information. Get real-time health status and diagnostics for a specific asset

04

get_maintenance_logs

Each log entry includes work order reference, technician details, parts replaced, labor hours, root cause analysis, and resolution notes. Use this tool to track maintenance history, identify recurring failure patterns, verify warranty service records, or audit compliance with preventive maintenance schedules. Filter by asset ID to focus on a specific device, or use date range and log type parameters to narrow the search. Access maintenance and repair logs for Honeywell industrial assets

05

get_operational_alerts

Alerts include equipment anomalies, threshold violations, process deviations, connectivity issues, and safety warnings. Each alert contains severity level, source asset, description, timestamp, and acknowledgment status. Use this tool to identify current operational issues, review recent incident history, or assess the overall health status of industrial processes. Filter by severity, status, or date range to narrow down results. List operational alerts and notifications from the Honeywell process monitoring system

06

get_process_metrics

Metrics include throughput rates, efficiency scores, uptime percentages, cycle times, and quality indices across production lines or individual assets. Use this tool to evaluate operational performance, identify bottlenecks, compare shifts or lines, and generate performance reports. Results can be filtered by time range, asset group, or specific metric categories to focus the analysis on relevant operational data. Get real-time and historical process performance metrics

07

get_production_data

Data is organized by production line, shift, or time period. Use this tool to analyze production trends, verify output targets, compare actual vs. planned production, or generate operational summaries. Filter by site, line, date range, or product type to focus the analysis on specific segments of the production operation. Retrieve production output and operational data from the Honeywell process system

08

get_scan_events

Each event includes timestamp, device ID, scan type, decoded data, and success/failure status. Use this tool to audit scanning operations, trace barcode or RFID read events, investigate scan failures, or analyze throughput patterns for specific devices or across the entire facility. Optionally filter by a specific asset ID to focus on one device. Retrieve scan event history from Honeywell scanning and mobility devices

09

get_shift_reports

Reports include output quantities, downtime events, quality metrics, safety observations, and operator notes. Use this tool to review historical shift performance, compare shift-to-shift results, identify recurring issues, or prepare management summaries. Optionally specify a shift ID to retrieve a single detailed report. Retrieve shift operation reports summarizing production activity

10

list_assets

Supports optional filtering by site, type, or status. Use this tool when you need to discover available assets, check device registration status, or build an overview of the industrial infrastructure. Returns asset IDs, names, types, locations, and current operational status for each registered device. List all registered assets and devices in the Honeywell Operational Intelligence platform

Troubleshooting Honeywell Process MCP Server with VS Code Copilot

Common issues when connecting Honeywell Process to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Honeywell Process + VS Code Copilot FAQ

Common questions about integrating Honeywell Process MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Honeywell Process to VS Code Copilot

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