Django Chainsaw MCP Server

Django Chainsaw is an MCP integration. Finds what will hurt in a Django project: cascades, N+1, unsafe migrations, tenant leaks.

Packages and local setup

The published pypi package is django-chainsaw-mcp, version 0.1.5. Its declared MCP transport is stdio.

The package declares DJANGO_CHAINSAW_PROJECT_PATH (required): Absolute path to the Django project to analyse - the directory containing manage.py, or whichever directory the settings module is importable from. This server must run in an interpreter that can import that project, so install it into the project's own environment rather than an isolated one.; DJANGO_CHAINSAW_SETTINGS_MODULE (required): Dotted path to the settings module, for example myproject.settings. Point it at the settings the site actually runs on: a base or partial module can import cleanly and load no models, and the server says so when that happens..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.5 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.