Bring Video Surveillance
to CrewAI
Create your Vinkius account to connect Arlo Smart to CrewAI and start using all 11 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Arlo Smart MCP Server?
Connect to Arlo Smart API and control your Arlo security cameras, review recordings, and manage security modes from any AI agent. Arm and disarm cameras, browse recorded videos, and monitor your home security through natural language commands.
What you can do
- Device Discovery — List all Arlo devices including basestations, cameras, doorbells, and floodlights
- Recording Access — Browse and download recorded videos from any camera with presigned URLs
- Recent Activity — Quickly check today's recordings across all cameras
- Security Modes — View and change automation modes (armed, disarmed, custom modes)
- Arm/Disarm — Enable or disable security monitoring on individual devices or basestations
- Recording Management — Delete old recordings to free up cloud storage space
- Metadata Access — Get detailed recording metadata including duration, timestamps, and download links
How it works
- Subscribe to this server
- Enter your Arlo authentication token
- Start controlling your Arlo security system from Claude, Cursor, or any MCP-compatible client
Your AI becomes a security assistant, helping you monitor recordings, manage security modes, and protect your home.
Who is this for?
- Homeowners — monitor security cameras and review recordings through natural language
- Property Managers — manage Arlo security systems across multiple properties
- Security-Conscious Users — arm/disarm cameras and check recent activity remotely
- Smart Home Enthusiasts — integrate Arlo cameras into broader home automation workflows
- Travelers — check home security recordings and adjust security modes while away
Built-in capabilities (11)
This enables motion detection and recording for the device. USE WHEN: - User wants to enable security monitoring - User asks to "arm the cameras" or "turn on security" - User wants to enable motion detection and recording - User is leaving home and wants security enabled PARAMETERS: - deviceId (REQUIRED): Arlo device ID to arm EXAMPLES: - "Arm the front door camera" → call with deviceId="FRONT_DOOR_ID" - "Enable security on the backyard camera" → call with deviceId="BACKYARD_ID" - "Arm the basestation" → call with deviceId="BASESTATION_ID" Arm an Arlo device (enable security monitoring)
This action is permanent and cannot be undone. USE WHEN: - User wants to free up cloud storage space - User wants to remove old or unwanted recordings - User asks to "delete recordings from [date]" - User is managing their Arlo cloud storage PARAMETERS: - recordings (REQUIRED): JSON array of recording objects to delete (from get_arlo_recordings response) EXAMPLES: - "Delete these recordings" → call with recordings=[{...}] Delete Arlo recordings from the library
This disables motion detection and recording for the device. USE WHEN: - User wants to disable security monitoring - User asks to "disarm the cameras" or "turn off security" - User wants to disable motion detection temporarily - User is home and wants to disable security PARAMETERS: - deviceId (REQUIRED): Arlo device ID to disarm EXAMPLES: - "Disarm the front door camera" → call with deviceId="FRONT_DOOR_ID" - "Disable security on the backyard camera" → call with deviceId="BACKYARD_ID" - "Disarm the basestation" → call with deviceId="BASESTATION_ID" Disarm an Arlo device (disable security monitoring)
Shows whether the device is armed, disarmed, or in a custom mode. Get the current automation modes for an Arlo device
Get detailed metadata for an Arlo recording
Returns presigned URLs for downloading video files along with metadata like duration, device ID, and creation date. USE WHEN: - User wants to download or view Arlo recordings - User needs to check what was recorded on specific dates - User is reviewing security footage - User asks "show me recordings from [date range]" PARAMETERS: - dateFrom (REQUIRED): Start date in YYYYMMDD format (e.g. 20260407) - dateTo (REQUIRED): End date in YYYYMMDD format - deviceId (OPTIONAL): Filter by specific device ID EXAMPLES: - "Get recordings from April 7 2026" → call with dateFrom="20260407", dateTo="20260407" - "Show recordings from last week" → call with dateFrom="20260331", dateTo="20260406" - "Get recordings for camera XYZ on April 5" → call with dateFrom="20260405", dateTo="20260405", deviceId="XYZ" Get Arlo camera recordings for a date range
Useful for quickly checking recent security activity. Get recent Arlo recordings from the last 24 hours
Basestations are the central hubs that connect wireless Arlo cameras to your network. List Arlo basestation/hub devices only
List Arlo camera devices only
Each device includes deviceId, deviceName, deviceType, state, and connection status. USE WHEN: - User wants to see all their Arlo security devices - User needs to find device IDs for other commands - User is exploring their Arlo security setup - User asks "what Arlo devices do I have" EXAMPLES: - "List all my Arlo devices" → call with no params - "Show my Arlo security devices" → call with no params - "What Arlo cameras and basestations do I have?" → call with no params List all Arlo devices (basestations and cameras)
Common modes: mode0 (disarmed), mode1 (armed), mode2 (armed with all motion). You can also use custom mode IDs created in the Arlo app. USE WHEN: - User wants to arm or disarm their Arlo security system - User wants to switch between different security modes - User asks to "arm the cameras" or "disarm the system" - User wants to enable/disable motion detection PARAMETERS: - deviceId (REQUIRED): Arlo device ID - mode (REQUIRED): Mode identifier (mode0=disarmed, mode1=armed, mode2=armed all motion, or custom mode ID) EXAMPLES: - "Arm the front door camera" → call with deviceId="FRONT_DOOR_ID", mode="mode1" - "Disarm all cameras" → call with deviceId="BASESTATION_ID", mode="mode0" - "Set to home mode" → call with deviceId, mode="mode_custom_home" Set the automation mode for an Arlo device
Why CrewAI?
When paired with CrewAI, Arlo Smart becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Arlo Smart tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Arlo Smart in CrewAI
Why run Arlo Smart with Vinkius?
The Arlo Smart connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 11 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Arlo Smart using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Arlo Smart and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Arlo Smart to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Arlo Smart for CrewAI
Every request between CrewAI and Arlo Smart is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
What Arlo devices are supported by this API?
The Arlo Smart API supports all Arlo devices including: Arlo Basestations (VMB4500, VMB5000), Arlo Cameras (Pro, Ultra, Essential, Go), Video Doorbells, Floodlight Cameras, and Arlo Lights. Use list_arlo_devices to see all devices in your account with their types and connection status.
How do I get an Arlo authentication token?
Authenticate with the Arlo API by sending your email and password to the Arlo auth endpoint (ocapi-app.arlo.com/api/auth). The API returns an authentication token that you can use for all subsequent requests. The token should be refreshed periodically as it expires after a set duration.
What's the difference between arming and disarming an Arlo device?
Arming (mode1) enables motion detection and automatic recording on the device. When armed, the camera will detect motion, record video clips, and send alerts to your phone. Disarming (mode0) disables motion detection and recording. The camera remains powered on but won't trigger recordings. Use arming when you're away and want security monitoring, and disarming when you're home to avoid false alerts.
How do I download recordings from Arlo?
Use get_arlo_recordings with a date range to retrieve recordings. The response includes presignedContentUrl for each recording — these are temporary download links that expire after a set time. You can directly download the MP4 video files using these URLs. For thumbnail images, use presignedThumbnailUrl. Use get_recent_arlo_recordings for a quick way to get today's recordings.
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.
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.
Explore More MCP Servers
View all →
Range
11 toolsKeep distributed teams in sync with async check-ins, team updates, and meeting tools that reduce unnecessary status meetings.
NeonCRM
10 toolsManage non-profit operations via NeonCRM — track donations, memberships, and events directly from your AI agent.
U.S. EIA Energy Data
10 toolsEquip your AI agent to access official U.S. energy statistics, track electricity generation, and monitor fuel prices via the EIA API.
Netlify Alternative
9 toolsModern web development platform — manage sites, deploys, and forms via AI.