Magg
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGG_LOG_LEVEL | No | Logging level: DEBUG, INFO, WARNING, ERROR, CRITICAL (default: INFO) | INFO |
| MAGG_READ_ONLY | No | Run in read-only mode. Set to 'true' to enable. | false |
| MAGG_PREFIX_SEP | No | Separator between prefix and tool name (default: '_') | _ |
| MAGG_AUTO_RELOAD | No | Enable/disable config auto-reload (default: true). Set to 'false' to disable. | true |
| MAGG_CONFIG_PATH | No | Path to config file (default: .magg/config.json) | .magg/config.json |
| MAGG_PRIVATE_KEY | No | Private key for authentication (RSA). Can be set instead of key file in ~/.ssh/magg/. | |
| MAGG_SELF_PREFIX | No | Prefix for Magg tools (default: 'magg'). Tools will be named as {prefix}{sep}{tool}. | magg |
| MAGG_STDERR_SHOW | No | Show stderr output from subprocess MCP servers (default: suppressed). Set to '1' to enable. | |
| MAGG_RELOAD_POLL_INTERVAL | No | Config polling interval in seconds (default: 1.0) | 1.0 |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proxyA | Main proxy tool for dynamic access to mounted MCP servers. This tool provides a unified interface for:
Annotations are used to provide rich type information for results, which can generally be expected to ultimately include JSON-encoded EmbeddedResource results that can be interpreted by the client. |
| magg_add_serverC | Add a new MCP server. |
| magg_remove_serverB | Remove a server. |
| magg_list_serversA | List all configured servers. Unlike the /servers/all resource, this tool also provides the runtime status of each server (mounted or not). |
| magg_enable_serverC | Enable a server. |
| magg_disable_serverC | Disable a server. |
| magg_search_serversC | Search for MCP servers online. |
| magg_smart_configureA | Use LLM sampling to intelligently configure and add a server from a URL. This tool performs the complete workflow:
Note: This requires an LLM context for intelligent configuration. Without LLM context, it falls back to basic metadata-based heuristics. For generating configuration prompts without sampling, use configure_server_prompt. |
| magg_analyze_serversB | Analyze configured servers and provide insights using LLM. |
| magg_statusB | Get basic Magg server status and statistics. |
| magg_checkC | Check health of all mounted servers and handle unresponsive ones. |
| magg_reload_configA | Reload configuration from disk and apply changes. This will:
Note: This operation may briefly interrupt service for affected servers. Config reload can also be triggered via SIGHUP signal on Unix systems. |
| magg_load_kitB | Load a kit and its servers into the configuration. |
| magg_unload_kitB | Unload a kit and optionally its servers from the configuration. |
| magg_list_kitsA | List all available kits with their status. |
| magg_kit_infoC | Get detailed information about a specific kit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| magg_configure_server | Generate an enriched prompt template for configuring a server from a URL. This prompt can be used with any LLM to generate server configuration. For automatic configuration with LLM sampling, use the smart_configure tool instead. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_all_servers_metadata | Expose all servers metadata as an MCP resource. |
| get_all_kits_metadata | Expose all loaded kits metadata as an MCP resource. Only returns kits that are currently loaded in memory. |
TDQS
Scored across 16 tools
Each tool has a generally distinct role—server lifecycle, health, kits, and proxy access are clearly separated. A few pairs (add_server vs smart_configure, status vs check) could be confused at a glance, but their descriptions sufficiently clarify the differences.
Most tools follow a consistent magg_verb_noun pattern (add_server, remove_server, list_servers, enable_server). However, 'proxy' lacks the magg_ prefix, and 'status'/'check' are not verb-object names, which is a minor deviation from the otherwise predictable pattern.
The set covers server management, configuration, health, kits, and proxy access. Slightly over the ideal 3-15 range, but each tool maps to a distinct operation, so the count is reasonable for the scope.
The surface covers the core lifecycle: add/remove/list/enable/disable servers, health checks, configuration reload, kit management, searching, and runtime access via proxy. Minor gaps like editing server config or getting detailed info on one server are not blocking since remove/re-add and list cover those needs.