Django MCP Server

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL

https://heyclau.de/entry/mcp/django-mcp-server

Source URLs

https://raw.githubusercontent.com/gts360/django-mcp-server/main/README.md, https://github.com/gts360/django-mcp-server

Brand

Django MCP Server

Brand domain

djangoproject.com

Brand asset source

brandfetch

Safety notes

Django MCP Server can expose Django model querysets, custom Python methods, DRF create/list/update/delete views, serializers, resources, and low-level FastMCP tools to an MCP client., Published DRF create, update, and delete tools can mutate application data if their serializers, views, and authentication rules permit it., The README notes that built-in DRF authentication classes, permission classes, filter backends, and pagination are disabled for published DRF tools in favor of MCP authentication; review this carefully before reusing production views., Query tools can evaluate QuerySets and return database records; restrict queryset scope and fields before exposing sensitive models., Require confirmation and application-level authorization before exposing write tools, email-sending methods, admin-like actions, or tools that touch customer, employee, financial, health, or regulated data.

Privacy notes

Django sessions, request headers, model names, field names, primary keys, QuerySet results, serializer output, DRF request bodies, custom tool arguments, and tool responses can be exposed to the MCP client., Exposed models may contain user accounts, permissions, customer records, orders, messages, files, logs, internal notes, audit trails, or application-specific secrets., Remote streamable HTTP deployments can move application data outside the original Django UI and audit path if MCP auth, OAuth metadata, and retention are not configured correctly., Stdio usage can still expose data through local MCP client logs, transcripts, and tool traces., Keep MCP endpoint access, serializer fields, queryset filters, and tool docstrings intentionally narrow for each app.

Author

Smart GTS

Submitted by

oktofeesh1

Claim status

unclaimed

Last verified

2026-06-06

• Django sessions, request headers, model names, field names, primary keys, QuerySet results, serializer output, DRF request bodies, custom tool arguments, and tool responses can be exposed to the MCP client.
• Exposed models may contain user accounts, permissions, customer records, orders, messages, files, logs, internal notes, audit trails, or application-specific secrets.
• Remote streamable HTTP deployments can move application data outside the original Django UI and audit path if MCP auth, OAuth metadata, and retention are not configured correctly.
• Stdio usage can still expose data through local MCP client logs, transcripts, and tool traces.
• Keep MCP endpoint access, serializer fields, queryset filters, and tool docstrings intentionally narrow for each app.

• Django 4 or 5 application with Python 3.10 or newer.
• mcp_server added to INSTALLED_APPS and mcp_server.urls included in the Django URL configuration.
• Review of which Django models, querysets, custom methods, DRF views, serializers, and request context should be exposed to MCP clients.
• Authentication classes configured through DJANGO_MCP_AUTHENTICATION_CLASSES before exposing non-public data over streamable HTTP.
• Local or deployment-specific plan for stdio, WSGI, ASGI, OAuth2, sessions, and Dynamic Client Registration when remote clients need access.

Show that Django MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/django-mcp-server.svg)](https://heyclau.de/entry/mcp/django-mcp-server)

Django MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field	Django MCP Server Django extension that exposes MCP endpoints and stdio transport for Django apps, with declarative model query tools, custom toolsets, DRF create/list/ update/delete tool publishing, serializer output, and MCP inspection. Open dossier	Burp Suite MCP Server PortSwigger's Burp Suite MCP Server extension connects Burp Suite to MCP clients through an SSE server or packaged stdio proxy for request, Repeater, Intruder, history, scanner, Collaborator, and configuration workflows. Open dossier	Colab MCP Server Connect Claude to a Google Colab runtime. Colab MCP starts a local FastMCP server and websocket proxy, waits for an authorized Colab-origin browser connection, then exposes the session's notebook and runtime tools to your MCP client over stdio. Open dossier	FunASR MCP Server MCP server example from FunASR that lets Claude transcribe local audio files with local speech recognition, automatic language handling, timestamps, and speaker labels when available. Open dossier
Next steps	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust	Review first	Review first	Review first	Review first
Review status	Not reviewed	Not reviewed	Not reviewed	Not reviewed
Package trust	Package not verified	Package not verified	Package not verified	Package not verified
Source provenance	Source-backed	Source-backed	Source-backed	Source-backed
Submitter	oktofeesh1	oktofeesh1	oktofeesh1	oktofeesh1
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	Django MCP Server	Burp Suite MCP Server	Colab MCP	FunASR
Category	mcp	mcp	mcp	mcp
Source	Source-backed	Source-backed	Source-backed	Source-backed
Author	Smart GTS	PortSwigger	Google Colab	FunASR
Added	2026-06-06	2026-06-06	2026-06-06	2026-06-06
Platforms	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Harness	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓Django MCP Server can expose Django model querysets, custom Python methods, DRF create/list/update/delete views, serializers, resources, and low-level FastMCP tools to an MCP client. Published DRF create, update, and delete tools can mutate application data if their serializers, views, and authentication rules permit it. The README notes that built-in DRF authentication classes, permission classes, filter backends, and pagination are disabled for published DRF tools in favor of MCP authentication; review this carefully before reusing production views. Query tools can evaluate QuerySets and return database records; restrict queryset scope and fields before exposing sensitive models. Require confirmation and application-level authorization before exposing write tools, email-sending methods, admin-like actions, or tools that touch customer, employee, financial, health, or regulated data.	✓Burp Suite MCP Server can send HTTP/1.1 and HTTP/2 requests, create Repeater tabs, send requests to Intruder, toggle Proxy Intercept, pause or resume Burp's task execution engine, and update the active message editor. In Burp Suite Professional it can also expose scanner issues and generate or poll Collaborator payloads for out-of-band testing. The extension includes approval flows for outbound HTTP requests and sensitive data access, but users can configure always-allow targets and disable some approval requirements. Configuration editing tools can import project-level or user-level Burp options when enabled in the extension, which can change proxy, scanner, target, and other Burp behavior. Use only on systems and applications where testing is authorized; active requests, Intruder traffic, scanner workflows, and Collaborator payloads can affect third-party services. Keep the MCP server bound to trusted local interfaces and avoid exposing the SSE server to untrusted networks.	✓Colab MCP runs a local websocket proxy and waits for a Google Colab browser session to connect before proxying session tools. The server creates a bearer-style proxy token and accepts a single authorized Colab-origin websocket connection at a time. A connected Colab runtime can execute code and interact with notebooks, outputs, files, variables, packages, and mounted resources depending on the session and tools exposed by Colab. Use disposable notebooks or reviewed development sessions before allowing Claude to run code or inspect outputs. Avoid connecting notebooks that have access to production data, cloud credentials, private datasets, paid accelerators, or long-running jobs unless the workflow has explicit approval.	✓The MCP server exposes a `transcribe_audio` tool that reads the local file path supplied by the agent. Configure clients so Claude can only request audio files from approved directories; do not expose arbitrary private folders or shared drives. First use can download FunASR model weights and dependencies from upstream model hosts; review network policy, cache location, and disk usage before use in restricted environments. Long recordings and GPU transcription can consume significant CPU, GPU, memory, and disk cache resources. Require confirmation before transcribing meetings, calls, interviews, voice notes, customer audio, regulated recordings, or files containing other people.
Privacy notes	✓Django sessions, request headers, model names, field names, primary keys, QuerySet results, serializer output, DRF request bodies, custom tool arguments, and tool responses can be exposed to the MCP client. Exposed models may contain user accounts, permissions, customer records, orders, messages, files, logs, internal notes, audit trails, or application-specific secrets. Remote streamable HTTP deployments can move application data outside the original Django UI and audit path if MCP auth, OAuth metadata, and retention are not configured correctly. Stdio usage can still expose data through local MCP client logs, transcripts, and tool traces. Keep MCP endpoint access, serializer fields, queryset filters, and tool docstrings intentionally narrow for each app.	✓Proxy HTTP history, WebSocket history, Organizer items, scanner issues, request and response bodies, headers, cookies, tokens, session identifiers, and Collaborator interaction data may be returned to the MCP client. The extension can read project-level and user-level Burp configuration; upstream code filters some configuration credentials when configured, but users should still treat exported options as sensitive. MCP prompts, responses, Burp logs, and client transcripts can retain target URLs, credentials, payloads, vulnerability details, and proprietary application behavior. The stdio proxy and SSE server bridge Burp traffic into the MCP client process; keep client configs, proxy paths, and Burp project files protected.	✓Notebook code, prompts, outputs, logs, variables, datasets, file paths, runtime metadata, package lists, browser session details, and generated websocket tokens can be visible to the MCP client and model provider. Colab notebooks may contain API keys, OAuth tokens, mounted Drive paths, secrets in environment variables, private model weights, customer data, or unpublished research. Local log files are created under a temporary Colab MCP log directory by default unless a log directory is specified. Review Google Colab, MCP client, model provider, and organization retention policies before sending notebook or runtime context to an assistant.	✓Audio recordings can contain voices, names, accents, speaker identity, background speech, locations, health details, financial details, customer data, credentials spoken aloud, or other sensitive personal information. The upstream MCP example performs local inference and does not require an API key, but MCP clients, model providers, logs, terminal output, transcripts, screenshots, and shared chats can still retain audio paths and transcription text. Generated transcripts, timestamps, and speaker labels may identify individuals or reveal confidential conversations. Model downloads and package installation can contact PyPI, ModelScope, Hugging Face, or other dependency hosts depending on the environment and model configuration.
Prerequisites	Django 4 or 5 application with Python 3.10 or newer. mcp_server added to INSTALLED_APPS and mcp_server.urls included in the Django URL configuration. Review of which Django models, querysets, custom methods, DRF views, serializers, and request context should be exposed to MCP clients. Authentication classes configured through DJANGO_MCP_AUTHENTICATION_CLASSES before exposing non-public data over streamable HTTP.	Burp Suite Community or Professional with Java extension support. Java and the `jar` command available for building and loading the extension. Gradle wrapper execution allowed for building `build/libs/burp-mcp-all.jar` from source. An MCP client that can connect to the Burp SSE server or run the packaged stdio proxy.	uv or uvx available to run the server from the GitHub repository. Local MCP client that supports `notifications/tools/list_changed`. Google Colab account and browser session you are authorized to use. Local machine access, because upstream documents that the MCP client must run locally.	Python environment with FunASR installed from PyPI or a reviewed source checkout. Local checkout or copy of `examples/mcp_server/funasr_mcp.py` from the FunASR repository. Audio files in an approved location and format such as WAV, MP3, FLAC, M4A, or OGG. Optional GPU, Apple silicon, or CPU device selection through `FUNASR_DEVICE`.
Install	pip install django-mcp-server Copy install	./gradlew embedProxyJar Copy install	uvx git+https://github.com/googlecolab/colab-mcp Copy install	pip install funasr Copy install
Config	{ "mcpServers": { "django": { "command": "python", "args": [ "manage.py", "stdio_server" ], "type": "stdio" } } } Copy config	Manual-only setup: ./gradlew embedProxyJar Copy config	{ "mcpServers": { "colab-mcp": { "command": "uvx", "args": ["git+https://github.com/googlecolab/colab-mcp"], "timeout": 30000 } } } Copy config	Manual-only setup: pip install funasr Copy config
Citations	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed

Source-backed guides for putting this to work.