mcp-factory
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| _hub.list_botsA | List all bots registered in the hub and their subprocess status. Returns a JSON object keyed by bot name. |
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 no possibility of confusing it with another. The tool's purpose is clearly stated and distinct.
The single tool name '_hub.list_bots' follows a consistent verb_noun pattern with a domain prefix, which is acceptable and predictable.
A single tool for a server named 'mcp-factory' is insufficient. The tool only lists bots, suggesting the server's scope is much broader, leading to a mismatch between tool count and implied functionality.
The server lacks tools for creating, updating, deleting, or managing bot subprocesses. An agent can only list bots, resulting in severe incompleteness for the apparent domain.