agy-mcp
Related Servers
Alternatives to agy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover, install, and manage SKILL.md skills from a Git-backed registry via MCP tools for search, install, and list operations.12 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables managing local repositories, CLIs, MCP servers, and skills via MCP tools, with inventory tracking, guarded updates, and Docker-sandboxed trials.MIT
- AlicenseNot gradedqualityBmaintenanceEnables managing a canonical library of agent skills and MCP servers, syncing them across multiple development harnesses, and adding, importing, or configuring them through MCP tools.14 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable agents to search, inspect, lint, and safely install Agent Skills from the skillmd registry mid-conversation.6 npm1MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for managing AI skills and tools from GitHub marketplaces, enabling discovery, installation, removal, and auto-updates via natural language or commands.-
- FlicenseNot gradedqualityDmaintenanceEnables Claude/MCP agents to search, list, get details, and generate install commands for skills, MCP servers, and connections from the DFL Forge skills registry.-
TDQS
Scored across 12 tools
Most tools target clearly distinct actions (list/read/search/install/delete skills vs. config get/set), but agy_list_skills and agy_skill_lock_status both report installed skill source info and could be confused. The detailed return formats and examples help resolve most ambiguity.
Tools consistently use the agy_ prefix with snake_case and a mostly verb_noun pattern like agy_list_skills and agy_set_config. Minor exceptions like agy_help, agy_version, and agy_skill_lock_status deviate from the verb_noun convention but remain readable and predictable.
12 tools is well-scoped for a server managing Antigravity skills, configuration, providers, and version info. Each tool has a defined role, and the count is appropriate without feeling bloated or sparse.
The skill lifecycle is well covered: list, read, search, install, delete, and GitHub-based install are all present, with config get/set and provider listing. Minor gaps exist such as no direct provider add/remove tool or config deletion, but these can be worked around via set_config.