AI assistants
Ask your AI assistant what IntelliSee saw.
The IntelliSee MCP connector gives MCP-compatible AI assistants read-only access to your deployment: alerts awaiting review, alert trends, the busiest cameras, and whether every appliance is online.
MCP connector · Model Context Protocol
- Alert records
- Alert trends
- Appliance and camera status
What stays out
- No images or video
- No recipient lists
- No changes
The connection
A standard connection, read-only by design.
The assistant reads alert records and system status. It does not see detection images or video, and it cannot change settings or send alerts.
What an assistant can read
Answers about your deployment, in plain language.
Deployment overview
Appliances and how many are online, cameras and how many are enabled, alerts in the last 24 hours, and how many alerts are still unreviewed.
Alert records
Alerts newest first, filtered to unreviewed, all, or false positives: time, appliance, camera, detection, risk, and whether each was reviewed or acknowledged.
Alert trends
Totals for the last 7 or 30 days, with false positives, unreviewed and acknowledged counts, a per-day view, and the top detections and cameras.
Appliances and cameras
Each appliance’s online status and alert activity, and each camera’s model, location, alerts in the last 7 days, and last alert time.
Try asking
Questions your team can ask.
- “Which alerts from last night are still unreviewed?”
- “Which cameras produced the most alerts this month?”
- “Is every appliance online right now?”
- “How many alerts did we mark as false positives in the last 30 days?”
What stays out
Sensitive detail stays in IntelliSee.
- No images or video
The connector reports whether an alert has an image or video. It never returns the image or video itself.
- No recipient lists
Who received an alert is not part of what the assistant can read.
- No changes
The connector reads records and status. It cannot acknowledge alerts, change settings, or route anything.
What MCP is
One open standard for connecting assistants to tools.
The Model Context Protocol is an open standard that lets AI assistants connect to outside tools and data through a consistent interface. A connector publishes what an assistant may read or do, and the assistant uses it on behalf of a signed-in person.
That means the same connector can work with the MCP-compatible assistant your organization approves, instead of a separate custom integration for each one.
In practice
Treat it like any other integration.
Decide who connects
Alert records include camera names and locations. Limit the connection to the people who already review alerts and manage the deployment.
Keep people in charge of response
An assistant helps people understand what happened. Alerts still go to your designated responders, and your procedures still decide what happens next.
Review it with IT and security
Cover authentication, which assistant is approved, what is logged, and how the assistant itself handles and retains the answers it receives.
Plan your next step
Bring your AI assistant plans into view.
Before your walkthrough
Bring the AI assistant your organization has approved, your identity and access requirements, and the people who will use and own the connection.
What we’ll work through
We’ll walk through what the connector reads for your deployment, how people connect and authenticate, and how access is granted and removed.
Discuss the MCP connector
Common questions
Integration planning questions
What is the IntelliSee MCP connector?
It connects MCP-compatible AI assistants to IntelliSee through the Model Context Protocol. An assistant can read your deployment overview, alert records and their review state, 7- and 30-day alert trends, and appliance and camera status. It is read-only and does not return detection images, video, or alert recipients. It helps people understand what happened; it does not replace alert routing to designated responders or your response procedures.
Who should join an integration walkthrough?
Include camera/VMS administration, IT networking, the notification or chat platform owner, the operational response owner, and your integrator if one supports the site. Each controls a different part of the workflow.
Build with IntelliSee
Bring the setup you have. Explore what comes next.
Share your existing platforms, the environments you support, and the response workflows you want to improve. We’ll help identify the right next conversation.