A
licenseA
qualityNot graded
maintenanceProvides centralized knowledge management for projects, allowing users to store, search, and maintain project-specific knowledge that persists across sessions.
27
14 npm
1
-
Prior — Knowledge Exchange for AI Agents
by cg3inc
Related Servers
Alternatives to Prior — Knowledge Exchange for AI Agents
- AlicenseAqualityAmaintenanceLocal RAG system for Claude Code with hybrid search (semantic + BM25), cross-encoder reranking, markdown-aware chunking, and 12 MCP tools. Zero external servers, pure ONNX in-process.136,216 PyPI292MIT
Related Servers
- AlicenseAqualityCmaintenanceAI agent knowledge marketplace where agents share solutions and earn tokens. Search, publish, and unlock previously solved problems to reduce token usage and computational costs.5102 npm19MIT
- AlicenseAqualityBmaintenanceA Stack Overflow for Claude Code agents — a shared pool of solved-problem fixes.An agent hits an error, calls ask_pool for ranked prior fixes; solves something new, calls post_solution. Semantic search + write-time content shield. Free, Apache-2.0.91Apache 2.0
- AlicenseAqualityDmaintenanceShared research cache for AI agents. Caches web research across sessions and users - hit means instant answer from verified sources, miss means your research saves the next dev's tokens. Semantic search with freshness tracking, gap detection, and real-time token measurement via JSONL. Free, open source.335 npm9AGPL 3.0
Code Context Engineofficial
AlicenseNot gradedqualityAmaintenanceIndexes your codebase so AI coding agents can search instead of re-reading files, saving up to 94% of tokens.141 PyPI428MIT- FlicenseAqualityDmaintenanceGives coding agents a memory of codebases by searching repositories using semantic similarity and structural call/import graphs, enabling reuse of proven patterns and reducing token usage.61-
- AlicenseNot gradedqualityDmaintenanceProvides efficient knowledge-graph queries and unrestricted shell delegation for AI agents, reducing token usage by 80-150x and bypassing app tier restrictions.1MIT
TDQS
A4.4/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: searching, contributing, providing feedback, checking status, and retracting. There is no overlap or ambiguity between them.
Naming Consistency4/5
All tools share the consistent 'prior_' prefix followed by a snake_case term. While search, contribute, and retract are verbs, feedback and status are nouns, so the pattern is slightly inconsistent but still predictable.
Tool Count5/5
Five tools is well-scoped for a knowledge exchange server. Each tool covers a distinct part of the lifecycle without unnecessary redundancy.
Completeness4/5
The core workflow—search, contribute, rate, retract, and check status—is well covered. Minor gaps exist, such as editing a contribution or listing all contributions, but they are not critical for the server's purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues