Django MCP Server

Created By
omarbenhamida year ago
Django MCP Server is a Django extensions to easily enable AI Agents to interact with Django Apps through the Model Context Protocol it works equally well on WSGI and ASGI
Overview

What is Django MCP Server?

Django MCP Server is a Django extension that enables AI agents to interact with Django applications through the Model Context Protocol (MCP). It works seamlessly on both WSGI and ASGI.

How to use Django MCP Server?

To use Django MCP Server, install it via pip, configure your Django app by adding it to your INSTALLED_APPS, and define MCP tools in your application.

Key features of Django MCP Server?

  • Exposes Django models as MCP tools for AI agents.
  • Allows easy integration with AI agents and MCP clients.
  • Supports both WSGI and ASGI applications without infrastructure changes.

Use cases of Django MCP Server?

  1. Enabling AI agents to query Django models.
  2. Integrating with tools like Google Agent Development Kit.
  3. Creating a seamless interaction layer for AI applications.

FAQ from Django MCP Server?

  • Can I use Django MCP Server with any Django application?

Yes! It can be integrated into any Django application.

  • Is there any authentication required?

By default, no authentication is enforced, but you can configure it using Django Rest Framework authentication classes.

  • How do I test the MCP server?

You can test it using the provided MCP Python SDK or any compatible MCP client.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
omarbenhamid
Star
31
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago