Django ORM Lens MCP Server

Static-analysis MCP server for Django models. 5 read-only tools. No DB, no boot, no creds. The django orm lens mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Your entire model graph — live in your editor sidebar, gating your CI, and answering your AI agent over MCP. All from static parsing: no database, no runserver, no working venv.

Adding it to your client

django-orm-lens on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

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

• uses — actions/checkout@v4
• repo — https://github.com/FROWNINGdev/django-orm-lens
• run — |
• list_apps — Every Django app in the workspace with model counts
• list_models — Flat app.Model list, optional app filter
• describe_model — Full field / relation / Meta detail for one model
• find_relations — Inbound + outbound relations for one model
• cascade_preview — Blast radius of one delete(), grouped by on_delete
• er_diagram — ER diagram — mermaid / dbml / d2 / plantuml / dot
• describe_migration_dependency — Per-app migration DAG: roots, leaves, cross-app deps
• suggest_indexes — Meta.indexes proposals from observed QuerySet usage
• signal_graph — Sender→signal→handler graph from @receiver decorators

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 Django ORM Lens.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the django orm lens mcp server does with a few real requests.

When to reach for it

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Django ORM Lens's toolset — uses, repo, run and 11 more — is a fair guide to whether it matches your workflow. It is maintained by FROWNINGdev; 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.