AgentBase MCP Server
Related Servers
Alternatives to AgentBase MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceSearch 60,000+ AI agent skills from ClawHub, LobeHub, Dify, and GitHub via MCP SSE or REST API. Free, no API key required.4MIT

plugandship-mcpofficial
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 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 gradedqualityAmaintenanceLets MCP-compatible clients and coding agents search, list, filter, and retrieve details from a curated catalog of 378 AI agent frameworks, developer tools, and automation repositories using natural language, with bilingual (English/Georgian) descriptions and category, language, and result-limit options. The same catalog is also reachable from the terminal via an accompanying command-line interface.MIT
- AlicenseBqualityDmaintenanceEnables AI agents to interact with the Clawslist marketplace to browse, create, and manage listings using the Model Context Protocol. It provides a comprehensive set of tools for agent registration, messaging, and offer management directly within MCP-compatible clients.1912 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables users to search and explore a curated collection of 378 AI agent frameworks, developer tools, and automation repositories using natural language from any MCP-compatible client such as Claude Code, Cursor, or Codex. It also exposes CLI commands to list repositories by category, retrieve individual entries, and view collection statistics.MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_featured retrieves high-quality files, get_instruction fetches a specific file by slug, list_categories shows available categories, and search_registry performs keyword searches. The descriptions reinforce these unique roles, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_featured, get_instruction, list_categories, search_registry) using snake_case throughout. This predictability enhances readability and usability, with no deviations in style or convention.
With 4 tools, the server is well-scoped for its purpose of accessing an instruction registry. Each tool serves a distinct function (browsing, fetching, categorizing, searching), and there are no redundant or missing tools that would suggest over- or under-engineering.
The tool set provides complete coverage for interacting with an instruction registry: it supports discovery (list_categories, search_registry), retrieval (get_instruction), and quality filtering (get_featured). No obvious gaps exist, as agents can navigate from browsing to accessing specific instructions seamlessly.