Ara Records MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARA_PASSWORD | No | Password for HTTP Basic Authentication | |
| ARA_USERNAME | No | Username for HTTP Basic Authentication | |
| ARA_API_SERVER | No | Base URL of the Ara API server | http://localhost:8000 |
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 |
|---|---|
| ara_queryA | Query Ara API endpoints with automatic pagination defaults (limit=3, order=-started) |
| watch_playbookA | Monitor a playbook execution in real-time. Returns detailed progress including task completion, current status, and execution timeline. Call repeatedly to track progress. |
| get_playbook_statusA | Get a quick summary of playbook execution status without detailed task information. Useful for checking if a playbook is complete or monitoring multiple playbooks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Ara Playbooks | List of recorded Ansible playbooks |
| Ara Plays | List of recorded Ansible plays |
| Ara Tasks | List of recorded Ansible tasks |
| Ara Hosts | List of recorded Ansible hosts |
| Ara Results | List of recorded Ansible task results |
| Ara Latest Hosts | Latest playbook result for each host |
| Running Playbooks | Currently executing Ansible playbooks (for real-time monitoring) |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: ara_query is for general API queries, get_playbook_status provides summary status, and watch_playbook offers real-time monitoring with detailed progress. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming is mostly consistent with a verb_noun pattern (e.g., get_playbook_status, watch_playbook), but ara_query uses a different prefix (ara_) which deviates slightly. Overall, the names are readable and follow a logical structure, with only minor inconsistency.
With only 3 tools, the count feels thin for a records or monitoring server, potentially limiting coverage of the domain. While the tools cover key functions, more operations might be expected for comprehensive interaction with Ara records or playbooks.
The tools cover querying, status checking, and monitoring, but there are notable gaps such as creating, updating, or deleting records or playbooks. This may cause agents to hit dead ends when full lifecycle management is needed, though core monitoring workflows are supported.