How to Use the Limble CMMS MCP in Cursor

Q: How do I configure the Limble CMMS server in Cursor?

Add the server entry to your .cursor/mcp.json file in your project root or your global MCP configuration file. Once added, toggle on Agent mode in the chat panel to let the editor invoke tools like listtasks.

Q: Can Cursor automatically update asset fields in Limble CMMS?

Yes, if you give the agent permission, it can call the updateassetfield tool directly from the composer panel. This is useful for updating runtime hours or calibration logs while testing your scripts.

Q: Can my team share the Limble CMMS MCP configuration in Cursor?

Yes, you can commit the .cursor/mcp.json file to your Git repository. Every developer on your team using Cursor will automatically have access to the same tools once they pull the latest main branch.

Build custom maintenance scripts and automate Limble CMMS updates directly from Cursor using real-time asset 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 Cursor

Create your Vinkius account to connect Limble CMMS to Cursor 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Generate production code in Cursor using MCP Server tools

Stop writing code against fake JSON stubs. This integration lets your Cursor agent query `list_assets` and `get_asset_details` to inject actual production hardware schemas directly into your files. Your Cursor agent writes precise integration scripts because it sees the exact custom fields returned by your live equipment. You don't have to manually check the API documentation to write a clean parser.

Build automated telemetry syncs in Cursor

Writing a script to sync PLC sensor data to your assets is fast when your editor has MCP access. Cursor runs `update_asset_field` in real time to verify your data payloads before you commit the code. You can write, test, and debug your telemetry mapping logic in a single Cursor session. The editor checks your work by reading the updated values directly from the physical machine's record.

Map inventory relationships while coding

Building a custom dashboard for your stockroom requires precise mapping of parts to machines. Cursor queries `list_parts` and `list_asset_part_relations` to show you exactly how your database links are structured. Your Cursor agent uses this live schema to write correct SQL joins or API queries for your application. You avoid runtime errors caused by mismatched database keys or outdated relations.

Setup guide

Set up Limble CMMS MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Limble CMMS MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Limble CMMS transactions." If the MCP tools are loaded correctly, Cursor will call the Limble CMMS tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/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 Cursor

Add the server entry to your `.cursor/mcp.json` file in your project root or your global MCP configuration file. Once added, toggle on Agent mode in the chat panel to let the editor invoke tools like `list_tasks`.

Yes, if you give the agent permission, it can call the `update_asset_field` tool directly from the composer panel. This is useful for updating runtime hours or calibration logs while testing your scripts.

Yes, you can commit the `.cursor/mcp.json` file to your Git repository. Every developer on your team using Cursor will automatically have access to the same tools once they pull the latest main branch.

No, Vinkius hosts and manages the server execution environment for you. Cursor connects directly to the cloud-hosted endpoint, so you do not need to install any local dependencies.

Your vendor lists and labor entries are retrieved via secure, ephemeral connections that bypass persistent storage. Vinkius processes these requests in isolated environments, ensuring your operational data never leaks to public LLM training sets.

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