curatedmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CURATOR_TELEMETRY | No | Set to 'false' to disable anonymous telemetry | true |
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 |
|---|---|
| search_serversA | Search the CuratedMCP catalog for MCP servers by keyword, category, or use case |
| get_server_detailsA | Get full details about a specific MCP server including install instructions |
| install_serverA | Get the manual install configuration snippet for an MCP server (use add_to_stack instead if you want it managed by Launcher) |
| list_categoriesA | List all available MCP server categories |
| add_to_stackA | Add an MCP server to your Launcher stack so its tools become available through Launcher in every AI client. The server's tools appear as |
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 5 tools
Tools are mostly distinct: search_servers finds servers, get_server_details retrieves details, list_categories browses categories, while install_server and add_to_stack both relate to making a server available but via different mechanisms. The overlap between install_server and add_to_stack is clarified by their descriptions, so confusion is unlikely.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_server_details, search_servers, install_server, list_categories, add_to_stack. The verbs are clear and the pattern is uniform across the entire set.
With only 5 tools, the server is well-scoped for a curated catalog. Each tool covers a distinct core function—searching, browsing, retrieving details, and two installation paths—without unnecessary bloat or sparseness.
The tool surface covers the primary lifecycle of discovering and installing MCP servers: search, filter by category, get details, and install via either manual config or Launcher integration. Minor gaps exist, such as no removal/uninstall tool, but the core workflows are complete.