mcp-django-shell 0.3.1

MCP server providing a stateful Django shell for AI assistants.

mcp-django-shell

A Model Context Protocol (MCP) server providing a stateful Django shell for AI assistants to interact with Django projects.

Requirements

• Python 3.10, 3.11, 3.12, 3.13
• Django 4.2, 5.1, 5.2

Installation

1. Install the package from PyPI.

   python -m pip install mcp-django-shell
   
   # or if you like the new hotness
   
   uv add mcp-django-shell
   uv sync
   

2. Add to your Django project's INSTALLED_APPS:

   DEBUG = ...
   
   if DEBUG:
       INSTALLED_APPS.append("mcp_django_shell")
   

[!WARNING]

Only enable in development!

Look, it should go without saying, but I will say it anyway - this gives full shell access to your Django project. Only enable and use this in development and in a project that does not have access to any production data. LLMs can go off the rails, get spooked by some random error, and in trying to fix things drop a production database.

Getting Started

mcp-django-shell provides a Django management command that MCP clients can connect to. Configure your client using one of the examples below.

Don't see your client? Submit a PR with setup instructions.

Claude Code

{
  "mcpServers": {
    "django_shell": {
      "command": "python",
      "args": ["manage.py", "mcp_shell"],
      "cwd": "/path/to/your/django/project"
    }
  }
}

Opencode

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "django_shell": {
      "type": "local",
      "command": ["python", "manage.py", "mcp_shell"],
      "enabled": true
    }
  }
}

Usage

mcp-django-shell provides an MCP server with a stateful Django shell for AI assistants. It sets up Django, maintains session state between calls, and lets the AI write and execute Python code directly against your project.

The MCP server comes with just two tools:

• django_shell - Execute Python code in a persistent Django shell session
• django_reset - Reset the session, clearing all variables and imports

Imports and variables persist between calls, so the AI can work iteratively - exploring your models, testing queries, debugging issues.

It wouldn't be an MCP server README without a gratuitous list of features punctuated by emojis, so:

• 🐚 One tool - django_shell executes Python code in your Django environment
• 🔄 Persistent state - Imports and variables stick around between calls
• 🧹 Reset when needed - django_reset clears the session when things get weird
• 🚀 Zero configuration - No schemas, no settings, just Django
• 🤖 LLM-friendly - Designed for AI assistants that already know Python
• 📦 Minimal dependencies - Just FastMCP and Django (you already have Django)
• 🎯 Does one thing well - Runs code. That's it. That's the feature.

Inspired by Armin Ronacher's Your MCP Doesn't Need 30 Tools: It Needs Code.

Development

For detailed instructions on setting up a development environment and contributing to this project, see CONTRIBUTING.md.

For release procedures, see RELEASING.md.

License

mcp-django-shell is licensed under the MIT license. See the LICENSE file for more information.