Agent Registry MCP
Related Servers
Alternatives to Agent Registry MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSelf-hosted governed project memory for coding agents, recording decisions, checkpoints, evidence, review state, and agent activity in PostgreSQL with pgvector while keeping maintainer control over what becomes reusable memory or instruction-grade guidance.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceServes focused, token-bounded context from a project-local SQLite structural code graph to AI coding agents, exposing indexed entities, Git relationships and recorded project memory for exploration, impact analysis and session continuity. Runs locally with a CLI, hooks, authenticated dashboard and optional plugin providers.67 npmMIT
- AlicenseNot gradedqualityBmaintenanceA persistent, trust-scored project memory for AI coding agents, backed by PostgreSQL + pgvector, providing durable memory of architecture decisions, bug patterns, and coding conventions.26 npm1MIT
- FlicenseNot gradedqualityAmaintenanceProvides a local-first persistent memory layer that AI coding agents can read and write during sessions, enabling semantic search and recall of project decisions, preferences, error patterns, research, and cross-project guidelines stored in local SQLite. It also exposes an optional task queue and orchestration tools for delegating autonomous coding work that reuses the same stored context.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to persistently save, search, and restore project context across sessions, including decisions, progress, file caches, checkpoints, and channel-based memory. It supports git-aware organization, batch operations, and shared memory across parallel sessions.228 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides persistent project memory for AI coding agents, enabling context retention across sessions via event logging, briefing generation, and querying.MIT
TDQS
Scored across 15 tools
Most tools clearly target a distinct resource+action pair (context/skill/project/memory/agent), and parallel search/get operations across resources are reasonably distinguishable. However, skill_resolve versus skill_get is ambiguous without descriptions, and memory_get versus memory_recent plus context_search versus context_get have overlapping retrieval semantics that an agent could easily misselect.
All 15 tools use consistent snake_case with a resource-first, action-second pattern (e.g. context_search, skill_get, memory_register, project_detect). The two *_status tools (registry_status, agent_status) fit the same resource_action convention rather than deviating from it.
15 tools is at the upper end but well-scoped for a registry spanning six resource domains (context, skill, project, memory, registry, agent), with roughly 2-3 tools per domain and no obvious redundancy.
The surface covers registration, lookup, and search for some resources, and memory has a full lifecycle including memory_transition. But there is no skill_register, no context_register, no update/delete operations for projects or contexts, and agent support is limited to a single status tool, leaving notable lifecycle gaps.