A
licenseNot graded
qualityD
maintenanceEnables AI assistants to perform semantic, hybrid, and filtered search on indexed local documentation with RAG capabilities.
2
MIT
langflow-kb
by mavha
Related Servers
Alternatives to langflow-kb
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to search and retrieve information from large technical documentation (OpenAPI specs, markdown) via intelligent chunking and semantic search.MIT
- FlicenseNot gradedqualityDmaintenanceEnables semantic search over Databricks docs, API reference, Terraform provider docs, and knowledge base via tools like search_databricks_docs and research.-
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to retrieve relevant sections from a repository's declared documentation scope using hybrid vector and full-text search, with incremental indexing.MIT
- FlicenseNot gradedqualityDmaintenanceEnables semantic search across documents and code repositories using RAG (Retrieval-Augmented Generation) with vector embeddings. Automatically indexes PDF documents and performs relevance-scored lookups through ChromaDB and sentence transformers.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to semantically search through indexed documentation websites and local code repositories using OpenAI embeddings and ChromaDB vector storage.-
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a distinct operation: listing components by category, semantic doc search, exact component description, exact field-catalog search, and KB status. search_docs (meaning-based, docs) vs search_fields (exact match, catalog) are clearly differentiated by description, and list_components vs describe_component differ by scope.
Naming Consistency4/5
All tools share the langflow_kb_ prefix and mostly follow snake_case verb_noun (list_components, search_docs, describe_component, search_fields). The lone noun-only 'status' is a minor deviation but still readable and predictable.
Tool Count5/5
Five focused tools are well-scoped for a read-only knowledge-base server, each earning its place with no redundancy. This is squarely in the ideal 3-15 range.
Completeness4/5
The surface covers listing, semantic doc search, exact component/field lookup, and artifact status, providing coherent lifecycle coverage for a read-only KB. Minor gap: no direct tool to fetch a complete doc page beyond ranked passages, but URLs are returned to work around it.
Maintenance
ActivityMaintained
ResponsivenessNo issues