"CodeQL static analysis tool and semantic code analysis platform" matching MCP servers:

A Model Context Protocol server for deep codebase understanding of Python projects, focusing on data analysis and scientific computing. It provides architectural analysis, pattern detection, dependency mapping, test coverage analysis, and AI-optimized context generation.

Score your agent's governance (0-100), lint MCP tool definitions, and estimate costs across all major models. Free diagnostic tools with no API key needed. Expert skill files on governance, economics, and system architecture available with free tier.

MCP server for comprehensive code analysis, navigation, and quality assessment across 25+ programming languages.

A local MCP server that indexes codebases into Neo4j and provides tools for code analysis, dependency visualization, and impact assessment.

Enables querying cross-repo code dependencies, HTTP routes, database tables, and queues via an MCP server using Cypher queries.

This MCP server enables AI models to analyze local Python codebases using abstract syntax trees, providing tools for file structure analysis, symbol search, import graphing, docstring auditing, and refactoring prompts without loading entire source files into context.

An MCP server that helps transfer C4 diagrams from DrawIO and PlantUML into a DocHub architecture repository.

An MCP server that analyzes and traces business code flows across your codebase, enabling developers to quickly understand the complete execution path of features from frontend to backend to database.

Enables coding agents to draw and edit Excalidraw diagrams on localhost by rendering Mermaid source into a live-updating canvas synced through a context file, with support for reusable icon libraries. No API key is required.

Enables interactive MATLAB development by allowing users to execute scripts and specific code sections, manage workspace variables, and capture generated plots. It integrates with the MATLAB Python Engine to provide persistent execution context for MCP-compatible clients.

MCP server that provides code intelligence by indexing configured repositories, extracting deterministic facts, and enabling graph queries, drift checks, and maps via Kuzu-backed MCP tools.

Local code-graph engine for AI coding workflows: static analysis of Rust, Cangjie, ArkTS, TypeScript/JavaScript, C/C++, Python, and Shell projects into symbols, imports, call graphs, and quality gates, with pre-commit change review and impact analysis. Read-only by design — never executes build scripts or uploads code.

Turns relational schemas into editable entity-relationship diagrams in draw.io, supporting live databases, SQL DDL, YAML/JSON specs, and existing .drawio files, with tools for managing tables, columns, and relations.

A design orchestrator that brings Superdesign capabilities to Claude Code as native tools, enabling AI-powered UI design, wireframing, component creation, and logo/icon generation without requiring Anthropic API keys.

Analyzes runtime data objects to suggest optimal UI component instructions for a low-code renderer using structural heuristics. It automatically maps data patterns to specific UI elements like tables, carousels, and cards to streamline interface generation.

Builds a semantic graph of codebases across 38 languages and exposes 42 MCP tools for structured code understanding, search, and impact analysis.

Static codebase analysis as MCP tools — give AI coding agents a map of your repo instead of letting them burn half their tokens rediscovering it file by file.

A tool for vibecoding personnel and non-programmers to perform static code audit, query knowledge graph, and generate project documentation via MCP protocol.

Semantic 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.

Provides agents with read-only access to local code architecture graphs (structure from tree-sitter, semantic summaries from LLMs), including per-workspace graph/config/status/rebuild tools, while enforcing that topology comes only from static analysis.