Skip to main content
Glama
jilavsky

axis-cam-mcp

by jilavsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_camerasA

List the configured cameras: name, description and address.

Never returns credentials - only the names of the environment variables they are read from.

grab_frameA

Capture one still frame from camera and return it as a JPEG.

If the device refuses the requested resolution, the frame is taken at the closest one it supports instead and the reply says so.

Args: camera: A name from list_cameras. resolution: "WIDTHxHEIGHT", e.g. "1280x720", or a device-specific preset name such as "D1". The camera scales server-side; omit for the camera's configured default. See camera_capabilities. compression: 0-100, where 0 is best quality and the largest file. rotation: 0, 90, 180 or 270 degrees. channel: Which video input to read on a multi-channel encoder, e.g. "3" or "quad". Omit on a single-sensor camera.

camera_infoA

Model, product number and firmware for camera.

The cheapest way to prove credentials and network reach are good without moving an image.

camera_capabilitiesA

What camera actually supports: resolutions, rotations and video inputs.

Ask before guessing a resolution on an unfamiliar device, or to find out which channel of a multi-channel encoder holds the view you want.

The listed resolutions are the WIDTHxHEIGHT values the device advertises. Most also accept named presets they do not advertise - an encoder taking 720x480 will usually take "D1", "4CIF", "CIF" and "QCIF" too.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct purpose: listing configured cameras, grabbing a frame, retrieving device metadata, and querying supported capabilities. The potential similarity between camera_info and camera_capabilities is resolved by clear descriptions covering different aspects of the camera.

Naming Consistency3/5

Names are all lowercase snake_case and readable, but the convention is mixed: list_cameras and grab_frame use verb_noun while camera_info and camera_capabilities are noun phrases with no verb. This is not chaotic, but it lacks a single predictable pattern.

Tool Count5/5

Four tools is well-scoped for a camera-focused MCP: enumeration, metadata, capabilities, and frame capture. Each tool earns its place and there is no redundant or filler functionality.

Completeness4/5

The tool set covers the core read-only camera workflow: discover cameras, verify connectivity, check capabilities, and capture still frames. Minor gaps such as continuous video capture, camera configuration, or PTZ control are plausible extensions but do not seem essential to the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources