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.5 npm43MIT
- 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 gradedqualityCmaintenanceAn 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.34MIT
- 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 26 tools
Most tools target clearly distinct operations: the clangd_* LSP queries (hover/definition/references/symbols) and workspace_* file operations are well-separated. The one real overlap is cmake_test vs cmake_run_test, which both run tests, but the descriptions distinguish CTest presets from a direct single-executable run.
Names follow a clean domain-prefix convention (cmake_*, clangd_*, workspace_*, process_*, toolset(s)_*) with predictable verb_noun or noun forms. Minor inconsistencies: singular/plural mismatch between processes_overview vs process_get and toolsets_list vs toolset_get.
26 tools sits at the upper bound, but they span five genuinely distinct domains (CMake build/test, clangd LSP, filesystem, process logs, toolsets), and each tool earns its place within its domain. It is slightly heavy but reasonable for a multi-domain build/dev server.
Coverage is strong: CMake has profiles/configure/build/test/run_test, workspace has read/write/edit/move/delete/mkdir/search, and clangd covers navigation and diagnostics. Minor gaps remain (no clangd completion/rename/code-action, no workspace copy), but the core workflows are complete.