An [MCP Server](https://modelcontextprotocol.io/introduction) to utilize Codelogic's rich software dependency data in your AI programming assistant.
An MCP Server to utilize Codelogic's rich software dependency data in your AI programming assistant. The codelogic mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 9 defined tools rather than through you.
The server ships on PyPI as There, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Everything the assistant can do here goes through one of these:
codelogic-method-impact — Pulls an impact assessment from the CodeLogic server's APIs for your codecodelogic-database-impact — Analyzes impacts between code and database entitiescodelogic-graph-capabilities — GET — discover supported relationship types, limits, and flags for the workspace materialized view (materializedViewId defaults fromcodelogic-graph-search — Search nodes by text query / q and/or identity_prefix; optional scan_space, limit, etccodelogic-graph-impact — Dependency / blast-radius style traversal from seed_node_idscodelogic-graph-path-explain — Shortest-path style explanation between from_node_id and to_node_idcodelogic-graph-validate-change-scope — Heuristic checklist / risk summary for a proposed change given seed nodes and proposed_change_summarycodelogic-graph-owners — Resolve a node by node_id or identity_prefix and surface property fields whose names contain "owner"Tools — The server implements eight tools: two impact tools plus six graph tools backed by the CodeLogic graph HTTP APIYou will need 5 environment variables: CODELOGIC_SERVER_HOST, CODELOGIC_USERNAME, CODELOGIC_PASSWORD, CODELOGIC_WORKSPACE_NAME, CODELOGIC_DEBUG_MODE. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Codelogic's toolset — codelogic-method-impact, codelogic-database-impact, codelogic-graph-capabilities and 6 more — is a fair guide to whether it matches your workflow. It is maintained by CodeLogicIncEngineering; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Codelogic's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| codelogic-method-impact | Pulls an impact assessment from the CodeLogic server's APIs for your code. |
| codelogic-database-impact | Analyzes impacts between code and database entities. |
| codelogic-graph-capabilities | GET — discover supported relationship types, limits, and flags for the workspace materialized view (materializedViewId defaults from CODELOGIC_WORKSPACE_NAME like other tools). |
| codelogic-graph-search | Search nodes by text query / q and/or identity_prefix; optional scan_space, limit, etc. |
| codelogic-graph-impact | Dependency / blast-radius style traversal from seed_node_ids. |
| codelogic-graph-path-explain | Shortest-path style explanation between from_node_id and to_node_id. |
| codelogic-graph-validate-change-scope | Heuristic checklist / risk summary for a proposed change given seed nodes and proposed_change_summary. |
| codelogic-graph-owners | Resolve a node by node_id or identity_prefix and surface property fields whose names contain "owner". |
| Tools | The server implements **eight** tools: two impact tools plus six **graph** tools backed by the CodeLogic graph HTTP API. |
{
"mcpServers": {
"codelogic": {
"command": "uvx",
"args": ["There"],
"env": {
"CODELOGIC_SERVER_HOST": "your-value",
"CODELOGIC_USERNAME": "your-value",
"CODELOGIC_PASSWORD": "your-value",
"CODELOGIC_WORKSPACE_NAME": "your-value",
"CODELOGIC_DEBUG_MODE": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CODELOGIC_SERVER_HOST | Endpoint or connection string the server talks to. | Optional |
| CODELOGIC_USERNAME | Configuration value read at startup. | Optional |
| CODELOGIC_PASSWORD | Configuration value read at startup. | Optional |
| CODELOGIC_WORKSPACE_NAME | Configuration value read at startup. | Optional |
| CODELOGIC_DEBUG_MODE | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.