KernelMind MCP
Related Servers
Alternatives to KernelMind MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a local, versioned knowledge graph of a software project, retrieving overviews, context packs, evidence, and explanations to make informed changes.MIT
- FlicenseNot gradedqualityBmaintenanceEnables LLMs to query a local commitment ledger and knowledge base extracted from email, calendar, and meeting transcripts, allowing natural language search for facts, people, and open commitments, and suggesting closures with evidence.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to search and query documentation from git repositories using hybrid search and structured metadata queries.1-
- AlicenseAqualityAmaintenanceEnables coding agents to query local notes, decisions, docs, and code with hybrid retrieval (BM25 + embeddings + reranking) and get path:line citations. It provides tools like rag_query for full-corpus search and search_knowledge for project-scoped knowledge recall.21MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query and analyze code across multiple repositories through a unified knowledge graph, with tools for symbol search, impact analysis, and graph algorithms.11 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search and retrieve context from GitHub issues, pull requests, releases, and documentation using hybrid semantic search and time-ordered activity scans.108 npmApache 2.0
TDQS
Scored across 16 tools
Every tool targets a distinct resource type and action. Search tools are differentiated by target (code, commits, patches, LKML, docs, LWN), and detail tools map one-to-one to those search targets. Even similar tools like search_kernel_code and lookup_symbol are clearly separated by broad search vs. exact symbol lookup.
All tool names follow a consistent lowercase snake_case verb_noun pattern (search_*, get_*, lookup_symbol, blame_line_range, analyze_*). No mixed conventions or ambiguous verbs; the naming scheme is uniform and predictable.
At 16 tools, the set is slightly above the typical 3-15 ideal range, but the breadth of the domain (code, commits, patches, LKML, docs, LWN, risk analysis) justifies each tool's existence. No redundant or trivial tools are present.
The tool surface provides full lifecycle coverage for kernel intelligence: search and retrieve operations for each data type (code, commits, patches, LKML, docs, LWN), plus specialized analysis (patch series, subsystem risk, file history, blame). No obvious gaps prevent an agent from answering kernel-related questions or performing deep investigations.