How do I get my API credentials?

Register a developer account at mydevices.com and create a new application in the developer portal to get your Client ID and Secret.

Does this work with Cayenne LPP?

Yes, as long as the data is correctly indexed in the Cayenne dashboard, this server can retrieve it via the REST API.

myDevices MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: myDevices
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to myDevices through Vinkius, pass the Edge URL in the `mcps` parameter and every myDevices tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="myDevices Specialist",
    goal="Help users interact with myDevices effectively",
    backstory=(
        "You are an expert at leveraging myDevices tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in myDevices "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

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

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 myDevices MCP Server

Connect your myDevices Cayenne account to empower your AI agents with IoT capabilities. This server allows for real-time monitoring and control of connected sensors and actuators.

When paired with CrewAI, myDevices becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call myDevices tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Device Visibility — List and inspect all connected IoT devices and their metadata
Telemetry Monitoring — Access real-time sensor data and historical telemetry records
Remote Control — Send commands to actuators and control hardware programmatically
Alert Management — Monitor and track IoT system alerts and notifications

The myDevices MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect myDevices to CrewAI via MCP

Follow these steps to integrate the myDevices MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from myDevices

Why Use CrewAI with the myDevices MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with myDevices through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

myDevices + CrewAI Use Cases

Practical scenarios where CrewAI combined with the myDevices MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries myDevices for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries myDevices, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain myDevices tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries myDevices against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

myDevices MCP Tools for CrewAI (8)

These 8 tools become available when you connect myDevices to CrewAI via MCP:

get_device

Get device details

get_sensor_data

Get current sensor value

get_sensor_history

Get historical sensor data

list_alerts

List IoT alerts

list_applications

List all applications

list_devices

List all IoT devices

list_sensors

List sensors for a device

send_command

Send command to device

Example Prompts for myDevices in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with myDevices immediately.

"List all my connected IoT devices."

"What is the current temperature reading from 'Sensor #1'?"

Troubleshooting myDevices MCP Server with CrewAI

Common issues when connecting myDevices to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

myDevices + CrewAI FAQ

Common questions about integrating myDevices MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.