Anava MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANAVA_HOST | Yes | IP address of your Axis camera | |
| ANAVA_PORT | No | HTTP port of the camera | 80 |
| ANAVA_PASSWORD | Yes | Camera password | |
| ANAVA_USERNAME | No | Camera username | root |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| anava_capture_analyzeC | Capture an image from camera and analyze it with AI |
| anava_capture_imageB | Capture an image from camera without analysis |
| anava_get_eventsC | Get historical events from camera |
| anava_monitor_eventsC | Monitor camera for real-time events |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: capture+analyze, capture-only, get historical events, and monitor real-time events. The descriptions make it impossible to confuse which tool to use for each specific camera/AI task.
All tools follow a perfect 'anava_verb_noun' pattern with consistent snake_case throughout. The naming is predictable and follows the same prefix+action+object structure across all four tools.
Four tools is ideal for this camera/AI monitoring server scope - it covers the essential operations (capture, analyze, historical data, real-time monitoring) without being too sparse or bloated. Each tool clearly earns its place.
The tool surface provides complete coverage for camera/AI monitoring: capture functionality (with and without analysis), historical data retrieval, and real-time monitoring. There are no obvious gaps in the core workflow for this domain.