Skip to main content

django-xprez-mcp

Admin-style MCP servers for Django. Register providers, models, admin classes and plain functions on a server; they become MCP tools, resources and prompts, filtered by the calling user's permissions.

Early development: phases 1 (core), 2 (models) and 3 (admin). See docs/design.md for the full design and roadmap.

Guides: getting started, permissions, security checklist.

# settings.py
INSTALLED_APPS = [..., "xprez_mcp", "xprez_mcp.contrib.tokens"]
XPREZ_MCP = {
    "PERMISSION": "myapp.use_mcp",  # required: who may use the server at all
}

# urls.py
from xprez_mcp import mcp

urlpatterns = [path("mcp/", mcp.urls)]

Clients send Authorization: Bearer <key>. With xprez_mcp.contrib.tokens users create keys under "MCP tokens" in the admin (shown once, stored hashed, revoked by deleting). Projects with their own token model leave the app out and set XPREZ_MCP["TOKEN_RESOLVER"] = "myapp.tokens.resolve" ((request, token) -> user | None).

# myapp/mcp.py: discovered automatically, like admin.py
from xprez_mcp import Provider, mcp, prompt, resource, tool


@mcp.register
class NotesProvider(Provider):
    namespace = "notes"

    @tool(read_only=True, permission="myapp.view_note")
    def search(self, ctx, query: str, limit: int = 20):
        """Search notes by title."""
        notes = Note.objects.filter(owner=ctx.user, title__icontains=query)
        return {"notes": list(notes.values("id", "title")[:limit])}

    @resource("notes://{id}", mime_type="text/markdown")
    def note(self, ctx, id: int):
        return Note.objects.get(owner=ctx.user, pk=id).text

    @prompt
    def summary(self, ctx, id: int):
        """Summarize one note."""
        return f"Summarize the note notes://{id}."


@mcp.tool
def ping(ctx) -> str:
    return "pong"
# myapp/mcp.py: tools generated from a model
from xprez_mcp import ModelProvider, mcp


@mcp.register(Note)
class NoteProvider(ModelProvider):
    fields = ["id", "title", "created"]
    search_fields = ["title"]
    filters = {"created_after": "created__gte"}
    actions = ["list", "get", "update"]  # notes_list, notes_get, notes_update

    def get_queryset(self, ctx):
        return Note.objects.filter(owner=ctx.user)

With many models, MCPServer(exposure="generic") exposes them through a few shared tools (models_list, records_search, record_get, ...) instead of tools per model. A provider can choose for itself with exposure.

# the admin, with exactly the permissions each user has there
from django.contrib import admin
from xprez_mcp import AdminProvider, mcp


@mcp.register(Note)
class NoteAdminProvider(AdminProvider):  # uses the registered NoteAdmin
    actions = ["list", "get", "update"]  # writes are opt-in
    admin_actions = ["publish"]          # ModelAdmin actions, opt-in


# the rest of admin.site (models registered above keep their own provider)
mcp.register_admin(admin.site, exposure="generic")

Write tools from installed third-party apps are held back until listed in XPREZ_MCP["ALLOW_WRITES"].

Development

python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"
.venv/bin/python -m django test xprez_mcp.tests --settings=xprez_mcp.tests.settings
.venv/bin/black --check .

Metadata

Release files for django-xprez-mcp 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-xprez-mcp 0.5.0
File Size Uploaded Provenance Actions
django_xprez_mcp-0.5.0.tar.gz 90.6 kB With provenance Details for django_xprez_mcp-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for django-xprez-mcp 0.5.0
File Interpreter ABI Platform Actions
django_xprez_mcp-0.5.0-py3-none-any.whl Python 3 none any Details for django_xprez_mcp-0.5.0-py3-none-any.whl

Total release size: 177.7 kB

Release files / django_xprez_mcp-0.5.0.tar.gz

Download URL django_xprez_mcp-0.5.0.tar.gz
Size 90.6 kB
Tags Source
SHA-256 checksum
How to use checksums
543e34a9743616258893e7f68cb4254133a002e0128166fe5d133b7441811f77
BLAKE2b-256 checksum
How to use checksums
e0f075f09fd5be514dcb5795a3281d6ca44be34267cf77efe4d6dba08c5fd4e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Release files / django_xprez_mcp-0.5.0-py3-none-any.whl

Download URL django_xprez_mcp-0.5.0-py3-none-any.whl
Size 87.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4f7c18934ee6449d82ebfaeba30800f9932b0ed627feb1bf5c5b188fe68ddc2e
BLAKE2b-256 checksum
How to use checksums
ac1b4420f78d2e9909b88f4e51fd77713e394501b81f217bd15b7a502d976371
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Security for django-xprez-mcp 0.5.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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for django_xprez_mcp-0.5.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page