Agent DVR

com.ispyconnectPublished by ispyconnect.comOfficial publisherv1.0.3Updated Oct 27, 2026

Ask your security cameras anything and set up alert rules in a sentence. Built into Agent DVR.

VerifiedStreamable HTTPWeb executableLocation & LifestyleSecurity & Monitoring

Overview

AI-generated overview

Connects an assistant to Agent DVR so it can query security cameras and create alert rules from plain-language requests.

What you can do
  • Ask questions about your security cameras in natural language
  • Set up camera alert rules described in a sentence
  • Work against an Agent DVR instance, either through the hosted endpoint or a local MCP endpoint on your network
When to use it
Useful if you already run Agent DVR for camera monitoring and want an assistant to answer questions about footage or configure alert rules without navigating the interface.
Requirements
An Agent DVR installation with its MCP endpoint reachable, set via AGENTDVR_MCP_URL for local use, or the hosted endpoint at ispyconnect.com. OAuth authentication is required; AGENTDVR_AUTH (username:password of an Agent DVR admin user) is needed only when the Protect API is enabled. The desktop extension package runs locally over stdio.
Before you install
The server asks for admin credentials for your Agent DVR account via AGENTDVR_AUTH, and OAuth is required. It can create alert rules, which changes your camera configuration. Camera data and requests may pass through the provider's hosted endpoint when used remotely.

Installation

In SourceWeft

  1. Open Agent DVR in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.ispyconnect%2Fagentdvr/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "agent-dvr": {
      "type": "http",
      "url": "https://www.ispyconnect.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.3LatestSep 20, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.