ForgeMCP
Related Servers
Alternatives to ForgeMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for C/C++ code analysis using clangd and clang tools, providing diagnostics, symbol search, include analysis, function listing, and code formatting.5MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that exposes Language Server Protocol features to external clients, allowing access to hover information, definitions, completions, references, and rename functionalities.8 npm42MIT
- AlicenseBqualityAmaintenanceAn MCP server that validates generated code against project structure and installed dependencies, catching undefined symbols, wrong API calls, dead code, and type mismatches in real time. It provides tools for project indexing, symbol/API checking, sandboxed execution, file scanning, and code analysis.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides semantic understanding of C++ codebases using libclang, allowing Claude to instantly find classes, functions, and their relationships without having to grep through thousands of files.33MIT
- FlicenseNot gradedqualityCmaintenanceA single MCP server that bridges to any LSP, enabling code intelligence features like hover, go-to-definition, references, and diagnostics for multiple languages via configurable language servers.1-
- AlicenseNot gradedqualityBmaintenanceA 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
TDQS
Scored across 25 tools
Tools are mostly well-separated by resource (workspace, process, clangd, cmake, toolset). Some ambiguity exists within the clangd and cmake families (e.g., clangd_* language features), but operation names and descriptions clarify intent.
Mostly consistent verb_noun with clear prefixes: workspace_*, cmake_*, clangd_*. Minor deviations: processes_overview and process_get, workspace_list vs. workspace_find_files, and toolset_get vs. toolsets_list, but overall predictable.
25 tools is on the higher side but reasonable for a multi-domain server covering workspace, CMake, clangd, and process management. Each domain contributes a focused set.
Covers essential operations for each domain: file CRUD, CMake configure/build/test, clangd diagnostics/navigation, process monitoring, and toolset listing. Minor gaps like process termination/start, CMake clean, or clangd rename may limit some workflows.