How to Use the Limble CMMS MCP in CrewAI

Q: How do CrewAI agents handle missing parts in Limble CMMS?

When an agent calls listparts and finds zero stock, it can pass that information to a vendor agent. The vendor agent then queries listvendors to find an approved supplier and draft a purchase request.

Deploy a coordinated team of autonomous maintenance agents using CrewAI and Limble CMMS.

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 CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Dispatch with CrewAI

This MCP Server uses `list_tasks` to let a dispatcher agent monitor incoming work orders while a separate supervisor agent schedules the team. The dispatch agent reads the active queue, categorizes the urgency, and hands the task to the best-suited technician agent. They collaborate in real-time to keep your facility running. If a task requires specific tools or components, the agents call `list_asset_part_relations` to verify parts availability. The supervisor agent can delay scheduling if the required items are out of stock, preventing wasted trips to the job site.

Autonomous Inventory Auditing

The server exposes `list_parts` to enable an inventory-focused agent to cross-reference stock levels against upcoming maintenance schedules using this MCP Server. If the agent notices that scheduled PMs will deplete critical spares, it alerts the purchasing agent. This keeps your warehouse stocked without manual oversight. To find where those spares are stored, the agent calls `list_locations`. Your crew can transfer parts between different facilities rather than placing unnecessary rush orders with suppliers.

Smart Asset Health Monitoring

This integration uses `update_asset_field` to let monitoring agents log machine runtime hours and temperature readings via the MCP Server. When an agent detects a reading outside of normal bounds, it immediately tasks a peer agent to draft a repair order. The entire diagnostic and escalation process happens autonomously. Your team can also run `get_asset_details` to pull historical performance baselines before making a decision. This prevents false alarms by letting the agents analyze the machine's specific operating context.

Setup guide

Set up Limble CMMS MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Limble CMMS tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Limble CMMS Analyst",
    goal="Access and analyze Limble CMMS data via MCP.",
    backstory="Expert analyst with direct Limble CMMS access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Limble CMMS transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Limble CMMS Analyst",
        goal="Access and analyze Limble CMMS data via MCP.",
        backstory="Expert analyst with direct Limble CMMS access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Limble CMMS transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

You pass the server's URL directly into the mcps list of your Agent configuration. For more advanced setups, use the MCPServerHTTP class to filter exactly which tools each agent can access.

Yes, your agents can execute parallel tool calls to speed up operations. While one agent runs list_assets to map the facility, another can query list_labor_entries to audit technician workloads.

When an agent calls list_parts and finds zero stock, it can pass that information to a vendor agent. The vendor agent then queries list_vendors to find an approved supplier and draft a purchase request.

Yes, you can set up a manager agent that delegates tasks to subordinate agents based on their specific tool access. The manager agent coordinates the workflow, ensuring tools are only called when necessary.

Your asset details, part relations, and labor entries are encrypted in transit and executed within secure, ephemeral V8 sandboxes. Your API keys are managed at the gateway level via the MCP connection, ensuring your agents never have direct access to raw credentials.

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