Shannon Lite MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shannon_healthA | Check Shannon Lite MCP runtime health (Docker, CLI resolution, config, workspace directory). |
| shannon_config_setB | Write ~/.shannon/config.toml for Shannon Lite providers (anthropic, custom_base_url, bedrock, vertex, router). |
| shannon_config_getA | Read ~/.shannon/config.toml and return masked credentials and active provider. |
| shannon_start_scanC | Start a Shannon Lite scan using URL/repo and optional config/workspace/output/router flags. |
| shannon_statusB | Get Shannon runtime status (Temporal + workers). |
| shannon_list_workspacesA | List Shannon workspaces and their high-level status. |
| shannon_get_workspaceC | Get detailed data for a single workspace. |
| shannon_read_workflow_logA | Read workflow.log for a workspace (tail by default). |
| shannon_read_reportB | Read a workspace report file from deliverables (defaults to comprehensive_security_assessment_report.md). |
| shannon_stopA | Stop Shannon worker and infra containers. Clean mode requires a confirmation token. |
| shannon_uninstallA | Stop Shannon runtime and remove ~/.shannon. Requires explicit confirmation token. |
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 11 tools
Each tool has a clearly distinct purpose: config, workspace management, health, scan execution, report reading, runtime control, and uninstall. No overlapping functionality.
All tools follow the consistent pattern `shannon_<verb>` or `shannon_<verb>_<noun>` (e.g., shannon_config_get, shannon_list_workspaces, shannon_start_scan, shannon_stop).
11 tools cover the essential operations for managing Shannon Lite without being excessive. The scope is well-defined for typical use cases.
Core workflows are covered: config, workspace listing, scan initiation, report reading, health checks, stop, and uninstall. Minor gaps exist (no explicit workspace creation or scan status polling), but agents can work around them.