swatplus-mcp
Related Servers
Alternatives to swatplus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local, SQLite-backed code index for Claude Code, exposed over MCP, enabling targeted code retrieval without external APIs.107 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that builds a deterministic, source-traceable knowledge index of any codebase, enabling glossary lookup, code graphs, and exact-token search with every fact linked to its source file and line.18 npm1MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that indexes local code repositories, extracting symbols and call graphs to give Claude precise, structural answers with real file paths and line numbers. Runs entirely locally with no network requests, for privacy-focused code understanding.73 npmMIT
- AlicenseNot gradedqualityCmaintenanceSemantic code index and gatekeeper that exposes 14 read-only MCP tools for AI agents, enabling symbol search, definition lookup, reference finding, and impact analysis via static analysis of codebases.17 npmMIT
- AlicenseNot gradedqualityDmaintenanceLocal-first, read-only MCP server for Claude Code that indexes and searches full-stack projects (FastAPI + React + PostgreSQL) with SQLite-backed FTS, cross-reference graph, and file-watcher auto-reload.3MIT
- AlicenseAqualityAmaintenanceExposes tools for AI assistants to query a persistent SQLite+FTS5 index of C/C++ symbols parsed from real build commands, enabling sub-millisecond lookup, full-text search, and natural-language explanation without hallucination.39560 PyPI8MIT
TDQS
Scored across 14 tools
Most tools target clearly distinct analysis questions: callers/callees, file_io/unit_users, loops/scope_at, and breakpoint all have separate purposes. The only real overlaps are file_io versus unit_users (both map routines to Fortran unit numbers/files) and writers versus breakpoint (both identify assignment sites), but the descriptions clarify these from different angles.
All names use lowercase snake_case and are readable, but the convention is mixed: some are imperative verb phrases like find_procedure and read_output, while others are bare nouns like callers, callees, writers, loops, and provenance, plus compounds like file_io, unit_users, and scope_at. This is not chaotic, but it lacks the uniform verb_noun pattern of a highly coherent toolset.
Fourteen tools is a well-scoped size for a complex SWAT+ source-code analysis server. Each tool addresses a distinct code-navigation or debugging concern, and none feel redundant enough to remove.
The server covers procedure discovery, call graphs, file/unit I/O, variable definitions, derived-type structure, loop context, breakpoint guidance, provenance, and output-file summarization, which is strong for its domain. Minor gaps exist, such as no direct source-text listing or a module/procedure inventory, but agents can still complete core analysis workflows.