Fdep MCP Server

🔌 MCP Protocol Compliant | 🏗️ 40+ Analysis Tools | ⚡ Real-time Queries. The fdep mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• initialize_database — Setup database and import FDEP data
• list_modules — Get list of modules with filtering
• get_module_details — Detailed module info with statistics
• get_functions_by_module — List all functions in a module
• search_modules — Pattern-based module search
• get_module_dependencies — Module dependency analysis
• get_code_statistics — Comprehensive codebase statistics
• get_function_details — Detailed function information
• search_functions — Search functions by pattern
• get_most_called_functions — Find frequently called functions
• get_function_call_graph — Function call hierarchy
• get_function_callers — Who calls this function

Configuration

You will need 4 environment variables: FDEP_PATH, LOG_LEVEL, DB_HOST, DB_NAME. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.13+ - UV package manager - PostgreSQL database (must be running) - FDEP output from Spider plugin (for comprehensive analysis)

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Fdep.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the fdep mcp server does with a few real requests.

When to reach for it

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Fdep's toolset — initialize_database, list_modules, get_module_details and 11 more — is a fair guide to whether it matches your workflow. It is maintained by maverox; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.