Code-Fundi MCP Server
OfficialRelated Servers
Alternatives to Code-Fundi MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server providing advanced code intelligence capabilities such as semantic search, dependency analysis, and natural language Q&A across multiple programming languages.MIT
- AlicenseNot gradedqualityAmaintenanceA production-ready MCP server that enables AI assistants to intelligently understand, analyze, edit, navigate, and review software projects with multi-workspace support, Git integration, and semantic search.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for local-first code intelligence, providing structural code graph, semantic search, and impact analysis to AI agents.2MIT
- FlicenseNot gradedqualityAmaintenanceAn MCP server that indexes codebases into a local knowledge graph, providing 52 AI tools for semantic search, call-graph traversal, git archaeology, and impact analysis to give AI agents deep understanding of code.2-
- AlicenseNot gradedqualityCmaintenanceMCP server that builds a dependency graph of your codebase, giving AI agents structural understanding to analyze impact, find context, and make safe modifications across languages and infrastructure.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents structured code understanding and precise code intelligence via local indexing of AST, call graphs, and semantic search.153 npm4Apache 2.0
TDQS
Scored across 27 tools
Most tools have clearly distinct purposes, but a few pairs could cause confusion: code-fundi-search vs. code-fundi-research (research wraps search with AI analysis), code-fundi-usage-stats vs. code-fundi-activity-stats, and the deprecated code-fundi-repo-readme overlapping with code-fundi-repo-blueprint. Descriptions are detailed enough to disambiguate, but the overlaps are noticeable.
All tools share the 'code-fundi-' prefix, but the remainder follows inconsistent patterns: some use verb_noun (list-repos, index-repo, list-files), others are noun phrases (repo-map, repo-blueprint, file-docs), and some are noun_verb (auth-authenticate, auth-verify). This mix of conventions makes it harder to predict tool names.
At 27 tools, the server exceeds the 25-tool threshold for 'too many'. The count is inflated by a deprecated tool (code-fundi-repo-readme) and a set of six auth-related tools that could be consolidated. While the broad scope partly justifies the number, the presence of redundant/deprecated tools makes it feel overbuilt.
The tool surface covers the core Code-Fundi workflows: repository indexing and listing, search/research, file and blueprint retrieval, stats, history, auth, API key management, chat, and model limits. Missing operations include repository removal (de-indexing) and more granular repo configuration, but these are minor gaps for the primary use cases.