django-mcp-inspector
Starts a Model Context Protocol server that exposes Django runtime information as resources, allowing AI agents to inspect a live Django project without any static file analysis.
Resources
| URI | Contents |
|---|---|
django://settings |
All settings (sensitive values redacted) |
django://apps |
Installed apps, labels, paths, model names |
django://urls |
URL pattern tree flattened to pattern / view / name |
django://models |
Every model's fields, types, and relations |
django://models/{app_label} |
Fields for a single app |
django://migrations |
Applied and pending migrations per app |
Usage
Zero project modification (recommended)
Run as an ephemeral tool — no changes to INSTALLED_APPS or requirements:
DJANGO_SETTINGS_MODULE=myproject.settings uv run --with django-mcp-inspector django-mcp-inspector
Pass --settings instead of the environment variable if you prefer:
uv run --with django-mcp-inspector django-mcp-inspector --settings myproject.settings
Exclude third-party app noise:
uv run --with django-mcp-inspector django-mcp-inspector --settings myproject.settings --exclude-site-packages
As an installed app
Add mcp_inspector to INSTALLED_APPS:
INSTALLED_APPS = [
...
'mcp_inspector',
]
Then run the management command:
python manage.py mcpserver
python manage.py mcpserver --exclude-site-packages
Connecting an MCP client
The server communicates over stdio. Point any MCP-compatible client (Claude Desktop, custom agent, etc.) at the process.
Example Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"django": {
"command": "uv",
"args": [
"run", "--with", "django-mcp-inspector",
"django-mcp-inspector", "--settings", "myproject.settings"
],
"env": {
"PYTHONPATH": "/path/to/your/project"
}
}
}
}
Requirements
- Python 3.12+
- Django 4.2+
- mcp 1.0+
Metadata
Release files for django-mcp-inspector 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_mcp_inspector-0.1.0.tar.gz | 5.4 kB | Without provenance | Details for django_mcp_inspector-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_mcp_inspector-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for django_mcp_inspector-0.1.0-py3-none-any.whl |
Total release size: 13.8 kB
Release files / django_mcp_inspector-0.1.0.tar.gz
| Download URL | django_mcp_inspector-0.1.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76eb2c48c189ae79e212d51426d2a5b0ca4c559452dee1a896b61277115f0d98
|
|
BLAKE2b-256 checksum How to use checksums |
e37287392d91babe60f821cdaeebddb6b1fc62596cb353cb00bdd82133fa3ea4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.18 {"installer":{"name":"uv","version":"0.9.18","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / django_mcp_inspector-0.1.0-py3-none-any.whl
| Download URL | django_mcp_inspector-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
732df72d18fa63fdba392c911995fbaac364146999d7de8529a98c8d6d63bf9a
|
|
BLAKE2b-256 checksum How to use checksums |
6ee509291efd8ad776517fc8235acff0d1dc326246dc91b5584b0c018171acf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.18 {"installer":{"name":"uv","version":"0.9.18","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for django-mcp-inspector 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.