Skip to content

Device Management

Verkada MCP connector

The Verkada connector brings your cameras, alerts, occupancy trends, license plate reads, and Helix events into Claude, ChatGPT, Cursor, and the Elaichi Agent, so your team can ask about what happened on site and log events without opening Verkada Command.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Verkada to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Verkada once

  1. Open Connections, choose Add connection, and pick Verkada.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Verkada API key. One person generates a token in Verkada and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

verkada
Verkada
Ayla Networks
Jamf
Iru (formerly Kandji)
ManageEngine MDM
Microsoft Intune
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Verkada to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Verkada to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Verkada to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Connect Verkada to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

Use cases

What teams do with Verkada through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • 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.”

See all 135 Verkada tools below

AI tools

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.

See it in Elaichi

What connecting Verkada gets you

6 screens from the product, each doing one job for your Verkada account.

The agent

Ask about camera alerts, read live answers.

Plain language questions return Verkada helix events, alerts and object counts.

  • helix events
  • event types
  • camera alerts
  • object counts

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Reach Verkada from any MCP client over OAuth, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

135 Verkada tools are ready to call.

Helix events, event types, camera alerts and analytics, with no custom code.

  • Create a Verkada helix event
  • Verkada helix events search
  • Verkada helix events bulk create
  • List all Verkada helix events
ElaichiTools
Tool Action Description
Create a Verkada helix event Create Create a new Helix event in Verkada Command by specifying attribute values for a previously defined Event Type. Returns: attribute_filters, keywords. Required: camera_id, event_type_uid, time_ms. Not all attribute keys tied to the Event Type need to be provided.
Verkada helix events search Search Search for Helix events in Verkada Command by camera, event type, time range, keywords, or attribute filters. Returns matching events with camera_id, event_type_uid, time_ms, attributes, and flagged for each result. No required parameters beyond authentication.
Verkada helix events bulk create Create Create multiple Helix events in a single asynchronous batch request in Verkada Command. Returns: attribute_filters, keywords. Required: items. Maximum 1,000 events per batch; events are processed asynchronously and the 202 response signals the job is queued, not completed.
List all Verkada helix events List Retrieve a single Verkada Helix Event posted to Command by specifying its camera, event type, and exact event timestamp. Returns: attribute_filters, keywords. Required: camera_id, time_ms, event_type_uid.
Verkada helix events bulk delete Delete Delete a Helix event from Verkada Command. Returns an empty 200 response on success. Required: camera_id, time_ms, event_type_uid.

Toolboxes

Every team gets its own Verkada toolbox.

Security, facilities and IT each see a curated set of Verkada tools.

  • Security operations
  • Facilities
  • IT
  • Loss prevention
ElaichiToolboxes
Name Source template Tools Created

Security operations toolbox

Verkada · camera alerts and incidents

Verkada starter 18 Mar 4, 2026

Facilities toolbox

Verkada · site cameras and occupancy

9 Mar 2, 2026

IT toolbox

Verkada · devices and event types

24 Feb 27, 2026

Loss prevention toolbox

Verkada · helix events and footage review

Verkada starter 6 Feb 19, 2026

Compliance toolbox

Verkada · audit trails and event types

31 Jan 30, 2026

Retail operations toolbox

Verkada · object counts by store

12 Jan 22, 2026

Shared connections

Teammates use Verkada without touching credentials.

Each connection shows who connected it and which teams and members share it.

  • Security EMEA
  • Head office
  • Warehouse north
  • Retail stores
ElaichiConnections
Connection Scope Status Access
VE

Verkada (Security EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
VE

Verkada (Head office)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
VE

Verkada (Warehouse north)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
VE

Verkada (Retail stores)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
VE

Verkada (IT operations)

Connected by Clara Nowak

Personal • Active Not shared
VE

Verkada (Facilities)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Verkada call is on the record.

When, who, what happened, type and resource for each helix event and alert.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Verkada Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Verkada Helix events Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Verkada Helix events List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, a digest posts back.

Verkada camera alerts are fetched, grouped, drafted, approved by a person, then posted.

Verkada digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch helix events

    Verkada

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Verkada

    Queued

Collections and dashboards

Verkada numbers arrive before anyone asks.

Four metrics, 14 days of helix events created, split by team, refreshed on schedule.

Verkada health

Refreshed 4 minutes ago · every 15 minutes · from the helix events collection

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one Verkada connection?

Yes. One person connects Verkada in Elaichi and shares it with a team, and nobody else ever handles or sees the API key. Each teammate still signs in to Elaichi as themselves, so every camera alert they check or Helix event they create is recorded under their own name in the audit log.

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 blocking the creation or deletion of Helix events or license plates of interest. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt can reach it.

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, and every other client at the same time.

Put Verkada in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.