dots-mcp
Related Servers
Alternatives to dots-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables coding agents to search an index of 22k+ MCP servers, agent skills and coding-agent plugins directly from chat, returning matches with stars, install commands and page links, plus trending repos and curated best-of topic lists. Read-only, no API key required, usable via a hosted HTTP endpoint or locally over stdio.4MIT- AlicenseNot gradedqualityCmaintenanceLets MCP clients such as Claude, Cursor, VS Code and Codex search a hand-checked directory of MCP servers, AI plugins and agent tools, returning summaries, copy-paste install configs and setup guides. Also supports keyword and category browsing plus troubleshooting guide lookups, working offline from a bundled snapshot when needed.MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving details of 41,000+ agent skills, MCP servers, Claude Code plugins, and agentic loops from any MCP-capable agent.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude, Claude Code and Cursor to keyword-search a directory of over 1,000 hand-picked productivity tools, apps, AI tools, courses and books, filtering by category, type, pricing and result limit, and to fetch a single listing by slug, page URL or exact name and list all categories with counts. It runs read-only over stdio with no API key, dependencies or tracking, making only a plain GET of the public catalogue.MIT
- AlicenseAqualityDmaintenanceMCP server for interfacing with the official Model Context Protocol registry. Enables Claude and other MCP clients to dynamically discover, browse, search, and manage MCP servers directly from GitHub.52MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.-
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.