How to Use the Limble CMMS MCP in VS Code Copilot

Q: How do I set up Limble CMMS for my team in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root and add the Vinkius MCP Server details. Once committed, any team member with VS Code 1.96 or higher can use the tools in Copilot Chat.

Q: Can VS Code Copilot modify asset records in Limble CMMS?

Yes, Copilot can write updates using the updateassetfield tool. The agent will always ask for your explicit confirmation in VS Code before running any write operations against your assets.

Connect VS Code Copilot to Limble CMMS to write team-wide automation scripts with live maintenance and vendor data.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Limble CMMS MCP to VS Code Copilot

Create your Vinkius account to connect Limble CMMS to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Limble CMMS with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Commit team-wide Limble CMMS MCP Server tools in VS Code

Get your entire engineering team on the same page. By committing an MCP Server configuration to your repository, every developer using VS Code Copilot gets instant access to `list_assets` and `list_locations`. You don't have to walk each teammate through manual setup steps. The configurations load automatically, letting everyone query facility data directly from their active VS Code workspace.

Debug maintenance workflows with live logs

Writing custom dispatch integrations is simpler when VS Code uses MCP to read live tasks using `list_tasks` to help you debug your conditional routing logic. If a technician's timesheet fails to sync, your VS Code Copilot agent queries `list_labor_entries` to inspect the exact format of the logged hours. You find the formatting bug in seconds instead of digging through raw database tables.

Write integrations for third-party vendors

Building a portal for your external suppliers requires accurate vendor data. This integration lets VS Code Copilot query `list_vendors` directly to verify your data models against actual vendor records. Your VS Code Copilot agent uses this live context to write clean, type-safe API wrappers that match your real-world operations. You eliminate integration bugs before pushing your code to staging.

Setup guide

Set up Limble CMMS MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Limble CMMS MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Limble CMMS tools listed. Try asking: "List my recent Limble CMMS transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "limble-cmms-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Limble CMMS. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Limble CMMS now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Limble CMMS MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and add the Vinkius MCP Server details. Once committed, any team member with VS Code 1.96 or higher can use the tools in Copilot Chat.

Yes, Copilot can write updates using the `update_asset_field` tool. The agent will always ask for your explicit confirmation in VS Code before running any write operations against your assets.

You only need the standard GitHub Copilot extension and VS Code version 1.96 or higher. The editor automatically detects the MCP Server configuration file in your workspace.

Vinkius manages the connection pooling and rate limits for you. If your team makes heavy concurrent calls to `list_parts`, the platform queues the requests to keep your integration running smoothly.

Your parts inventory and asset relations are accessed through a zero-trust architecture. Vinkius manages the API tokens securely, ensuring that sensitive facility schemas are never exposed to external networks or stored in local logs.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript