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) and 2 (models). See docs/design.md for the full design and roadmap.

# settings.py
INSTALLED_APPS = [..., "xprez_mcp"]
XPREZ_MCP = {
    "TOKEN_RESOLVER": "myapp.tokens.resolve",  # (request, token) -> user | None
    "PERMISSION": "myapp.use_mcp",  # required: who may use the server at all
}

# urls.py
from xprez_mcp import mcp

urlpatterns = [path("mcp/", mcp.urls)]
# 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(models="generic") exposes them through a few shared tools (models_list, records_search, record_get, ...) instead of tools per model.

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.2.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.2.0
File Size Uploaded Provenance Actions
django_xprez_mcp-0.2.0.tar.gz 51.7 kB With provenance Details for django_xprez_mcp-0.2.0.tar.gz

Built distribution (wheel)

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

Total release size: 103.8 kB

Release files / django_xprez_mcp-0.2.0.tar.gz

Download URL django_xprez_mcp-0.2.0.tar.gz
Size 51.7 kB
Tags Source
SHA-256 checksum
How to use checksums
ef71ca7e454d010bf4e8d159b41555c85c840a81875ad83ff997db3b436c1891
BLAKE2b-256 checksum
How to use checksums
e3b88214b7284d471c17e804dfbd6133eb48135ee5a79d4bf5ba219912603b1a
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.2.0-py3-none-any.whl

Download URL django_xprez_mcp-0.2.0-py3-none-any.whl
Size 52.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f1ab4a46bbb0ecb6d2c6ec88bd3cc38dcf64d3949b7ab7fc5f4d4d7308a32f78
BLAKE2b-256 checksum
How to use checksums
3cd8a63ea2a290294c6ae9cdeb206996b3196a8fbb7249962485f22db391d68f
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.2.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.2.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