Cams AI Device Agent

Run your device fleet by just asking. The Cams AI Device Agent connects to your Cams account and turns natural-language requests into real device operations — enroll a user, copy users between devices, pull an attendance summary, check which devices are online, or open a door — all backed by the same Cams APIs.

Get started Developer docs

Overview

Manage your biometric devices and attendance in plain English — enroll users, query logs, check device health, and open doors through a natural-language AI agent.

The Cams AI Device Agent is a natural-language interface to the Cams biometric platform, exposed as an MCP connector your assistant can call. It authenticates with either an OAuth 2.0 bearer token or your legacy Cams client key and passcode, then performs device and attendance operations on your behalf: adding, enrolling, finding, listing, and copying device users; pulling attendance logs and summaries; checking device health and connectivity; analyzing device activity; resetting device queues; and opening doors. It lets non-developers operate the platform conversationally while developers automate workflows without writing API plumbing.

AGENTMCP connectorNatural languageREST (backend)

Built for

Administrators, HR teams, and developers who want to operate and automate Cams devices and attendance through a conversational AI interface.

biometric AI agentnatural language device managementattendance AI assistantMCP biometric connectorconversational attendanceAI device controlenroll user AIopen door AI agent

Capabilities

What it does

Conversational User Management

Add, enroll, find, list, and copy device users by asking in plain language.

Attendance on Demand

Pull attendance logs and summaries without building queries or reports.

Device Health & Activity

Check device health, ping connectivity, and analyze activity across your fleet.

Access Control

Open doors and review which devices a user is enrolled on.

Features

Everything included

Natural-language control of device and attendance operations through an MCP connector
User management: add, enroll, find, list, and copy users across devices
Attendance access: pull attendance logs and summaries on demand
Device operations: check device health, ping connectivity, analyze activity, reset device queues
Access control: open doors and list which devices a user is enrolled on
Hybrid authentication: OAuth 2.0 bearer (RS256 JWT) for MCP/Claude connectors, or legacy Cams client key and passcode
Backed by the same Cams APIs, so results match the rest of the platform

Build with Cams AI Device Agent

Grab a key, read the docs, and ship. Our team helps with your first integration.

Talk to an engineer WhatsApp

FAQ

Common questions

What can the Cams AI Device Agent do?

It manages device users (add, enroll, find, list, copy), pulls attendance logs and summaries, checks device health and connectivity, analyzes activity, resets device queues, and opens doors — all from natural-language requests.

How does it authenticate?

It supports hybrid authentication: an OAuth 2.0 bearer token (the portal mints RS256 JWTs verified via JWKS) or your legacy Cams client key and passcode. Both resolve to your own account, devices and data.

Do I need to write code to use it?

No. It exposes the platform as a natural-language MCP connector, so you can operate devices conversationally, while developers can still automate workflows on top of it.