ART-CLI
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ART_HOME | Yes | Absolute path to the target home directory used for the ART-CLI installation. The MCP server is started with: python art.py --home "<absolute-target-home>" mcp |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| artC | One ArtCraft entry. Start with catalog/guide, then search and describe for exact native schemas. execute/batch start only selected native apps; explicit save/export required. All raw vendor CLI functions through native; resources/prompts through rpc. Not automatic live GUI control. |
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 1 tool
With only one tool there is literally no opportunity for misselection, so the set cannot be ambiguous across tools. However, the single tool's own purpose is dense and opaque (catalog/guide/search/describe/execute/batch/rpc/native all funneled through one entry point), which makes its scope hard to pin down.
There is no set of names to compare, so no inconsistency exists, but 'art' is a bare noun that establishes no verb_noun convention and is vague about what it does. It is readable but not descriptive of the underlying dispatch behavior.
A single tool is far too few for a server that apparently fronts an entire ArtCraft/vendor CLI with catalog, search, describe, execute, batch, and rpc surfaces. Everything is collapsed into one catch-all entry, forcing the agent to guess subcommands rather than choose a tool.
The description implies coverage of all native CLI functions plus a resources/prompts rpc bridge, so capability may exist behind the single tool. But the surface itself exposes no discrete, discoverable operations, leaving the agent dependent on self-describing catalog/guide steps to reach coverage.