dots-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOTS_LIST_URL | No | Override the source URL of the community-curated awesome-dots list. The list is fetched from GitHub and cached for 10 minutes. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dots_resourcesA | List resources about OpenAI Dots from the awesome-dots list, optionally filtered by section (e.g. Official, News & Coverage, Tools & Integrations). |
| search_dots_resourcesB | Search the awesome-dots list for OpenAI Dots guides, news, tools and use cases by keyword. |
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 2 tools
list_dots_resources and search_dots_resources both retrieve from the same dataset, but the list vs. keyword-search split is a clear, conventional distinction. An agent can easily choose the right tool based on whether it wants to enumerate/filter by section or query by keyword.
Both names use consistent snake_case with a verb_noun pattern (list_dots_resources, search_dots_resources) and share the same noun phrase. There is no deviation or mixed convention.
Two tools is on the thin side for a resource-access server; while both are warranted, the surface feels minimal. A third tool (e.g., get resource details) could round it out, but the current count is not unreasonable for a narrow, read-only list.
The domain is a curated resource list about OpenAI Dots; listing (with optional section filter) and keyword search cover the primary retrieval needs. However, there is no explicit operation to fetch a single resource by ID or to list available sections, leaving minor gaps an agent may need to work around.