Verkada MCP connector
The Verkada connector brings your cameras, alerts, occupancy trends, license plate reads, and Helix events into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so your team can ask about what happened on site and log events without opening Verkada Command.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize camera alerts from the warehouse cameras this week.
Working in Verkada with Elaichi
-
Verkada helix events search
-
List all Verkada helix events
-
List all Verkada helix event types
How to connect Verkada to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Verkada MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Verkada MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Verkada MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Verkada MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Verkada MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Verkada to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Verkada through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Verkada is logged.
-
Security
Review overnight camera alerts by site
Ask for every camera alert from the loading dock cameras since closing, and get a plain summary of what fired and when so the morning shift knows where to look first.
-
Facilities
Check how busy a building really is
Pull occupancy trends and people counts for the lobby, the cafeteria, or a whole floor over the past month, and see which spaces are over capacity and which sit empty.
-
Loss Prevention
Watch for a vehicle of interest
Add a plate to the license plates of interest list after an incident, then ask whether it has appeared at any lot since, pulling the matching plate images for the report.
-
Operations
Log a point-of-sale event against footage
Create Helix events for register voids, deliveries, or door props so each one is stamped on the camera timeline, then search those events later by type or time window.
-
Retail
Compare foot traffic across stores
Ask for peak object counts at each store entrance for the last two weeks and compare locations side by side to plan staffing and opening hours.
-
IT
Keep Helix event types and feeds tidy
List and update Helix event types in bulk, check the settings that stream Verkada data to other systems, and confirm a batch job finished without clicking through every page in Command.
Try asking
- “Summarize camera alerts from the warehouse cameras this week.”
- “Create a helix event for the loading dock incident.”
- “Show max object counts by camera for yesterday.”
What connecting Verkada gets you
6 screens from Elaichi, each doing one job for your Verkada account.
Ask Elaichi to work across your apps.
Summarize camera alerts from the warehouse cameras this week.
Create a helix event for the loading dock incident.
Show max object counts by camera for yesterday.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about camera alerts, read live answers.
Plain language questions return Verkada helix events, alerts and object counts.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Reach Verkada from any MCP client over OAuth, no SDK, no shared key.
Tool catalog
135 Verkada tools are ready to call.
Helix events, event types, camera alerts and analytics, with no custom code.
Toolboxes
Every team gets its own Verkada toolbox.
Security, facilities and IT each see a curated set of Verkada tools.
Shared connections
Teammates use Verkada without touching credentials.
Each connection shows who connected it and which teams and members share it.
Audit log
Every Verkada call is on the record.
When, who, what happened, type and resource for each helix event and alert.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Verkada digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch helix events
Verkada
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Verkada
Queued
Automations
A schedule fires, a digest posts back.
Verkada camera alerts are fetched, grouped, drafted, approved by a person, then posted.
Verkada health
Refreshed 4 minutes ago · every 15 minutes · from the helix events collection
Helix events
1,284 ↓ 12%
Event types
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Helix events created
Last 14 days
By team
Share of activity
Security EMEA 34%
Head office 27%
Warehouse north 21%
Retail stores 18%
Collections and dashboards
Verkada numbers arrive before anyone asks.
Four metrics, 14 days of helix events created, split by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Verkada
All three can connect Verkada to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Verkada tools | Allow or restrict single Verkada tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Verkada call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Verkada tools for your AI agents
135 tools are ready to call through Elaichi's MCP endpoint the moment you connect Verkada, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Verkada to Claude?
First, connect Verkada in Elaichi by pasting a Verkada API key from your Verkada Command admin settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Verkada is available in the chat.
Does Verkada work with ChatGPT and Cursor as well as Claude?
Yes. Once Verkada is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Verkada once and every client your team uses can reach it.
What can an AI agent actually do with my Verkada data?
With Verkada connected, an agent can list recent camera alerts, report people and vehicle counts from a camera, show occupancy trends for a space, pull license plate images, and manage your list of license plates of interest. It can also create and search Helix events so incidents land on the camera timeline. Because Verkada has a lot of capabilities, short concrete asks such as "camera alerts at the warehouse since 6pm" work better than long paragraphs.
Does connecting Verkada give the AI access to every camera and site?
No. An agent working through Verkada in Elaichi only sees the cameras, sites, and events that the Verkada API key used to connect is allowed to see, and each person still signs in to Elaichi as themselves. An Elaichi administrator can narrow that further, for example limiting a toolbox to reading alerts and occupancy, but Elaichi can never grant more than Verkada already allows.
Can I stop an agent from deleting or changing things in Verkada?
Yes. Restrictions in Elaichi work per action, so you can allow reading Verkada camera alerts and occupancy trends while restricting the creation or deletion of Helix events or license plates of interest. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
What happens to a Verkada connection when someone leaves?
When a person is offboarded in Elaichi, their access to Verkada through every client ends at once. A Verkada connection shared with a team keeps working for everyone else, and if the person who connected it leaves, an administrator can reassign it. Disconnecting Verkada once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Verkada MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Verkada is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Verkada?
Yes. Both let Claude, ChatGPT or Cursor use Verkada. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Verkada call.
How is Elaichi different from Composio for Verkada?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Verkada: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Verkada in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot