strands-hub-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USE_S3 | Yes | Must be true | |
| AGENT_HUB_BUCKET | Yes | S3 bucket name | |
| AGENT_HUB_REGION | Yes | AWS region |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hub_statusA | Return the effective hub configuration (sanitized) used by this server. |
| registry_list_agentsA | List registered agents (optionally filtered by tag). |
| registry_get_agentB | Get a single agent registry entry. |
| registry_update_metadataB | Update allowlisted metadata fields for an existing agent. |
| prompts_get_currentC | Get the current system prompt content for an agent (cached locally by strands-hub). |
| prompts_get_versionC | Get a specific system prompt version content for an agent. |
| prompts_list_versionsB | List prompt versions for an agent from S3 (versions.json if present). |
| prompts_create_versionA | Create a new prompt version (append-only). Does NOT modify current.txt.
|
| metrics_listC | List metrics objects in S3. |
| metrics_getA | Fetch a metrics JSON object by S3 key. |
| sessions_listC | List session IDs (prefixes) under Uses S3 CommonPrefixes (Delimiter="/") so it matches |
| sessions_get_session_jsonA | Fetch and parse |
| sessions_list_agentsB | List agent IDs under |
| sessions_get_agent_jsonB | Fetch and parse |
| sessions_list_messagesB | List message keys under |
| sessions_get_message_jsonC | Fetch and parse a message JSON object. message_key may be either a basename like |
| sessions_get_rawA | Fetch a session object by S3 key and return parsed JSON when possible. This is intentionally "raw" because session format is owned by |
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 17 tools
Most tools map to distinct resources and actions, with clear domain prefixes (registry, prompts, metrics, sessions). However, sessions_get_session_json and sessions_get_raw both fetch session data and could be confused, as could registry_get_agent vs sessions_get_agent_json despite their different contexts.
Naming follows a consistent <domain>_<verb>_<object> pattern for nearly all tools, such as registry_list_agents and sessions_get_message_json. The main deviation is hub_status, which lacks a verb unlike the rest, and sessions_get_raw uses an adjective instead of a specific object.
17 tools is slightly above the typical well-scoped range, but the count is justified by the five distinct domains and the deep session hierarchy. Each tool serves a specific retrieval task, making the count reasonable rather than bloated.
The read-focused surface is fairly complete for inspection: sessions are traversable from ID down to message content, prompts have version listing/creation, and metrics are accessible. Minor gaps include no delete/create in the registry and no write operations for sessions, but these may be intentionally outside the server's scope.