Changelog¶
All notable changes to Django Admin MCP are documented here.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[Unreleased]¶
[0.11.1] - 2026-10-20¶
Admin history shows changes to author-like fields again.
Fixed¶
- Admin history no longer redacts fields such as
author,authorityorauthored_at. The audit-log redactor matchedauthas a substring, so any change to anauthorforeign key was logged as***REDACTED***. Keys that containauthanywhere else (auth_token,basic_auth,authorization,authorize_url, ...) are still redacted. (#127, thanks @vishalhabib99)
[0.11.0] - 2026-10-16¶
The endpoint can now run over stdio, and tool failures are reported the way the MCP spec describes.
Added¶
mcp_stdiomanagement command serves the endpoint over stdio. Clients that can only launch a local process, and registries that boot a server to inspect its tools, runpython manage.py mcp_stdio --token mcp_<key>.<secret>(or setDJANGO_ADMIN_MCP_TOKEN). Each newline-delimited JSON-RPC message goes through the same code path asPOST /mcp/, so authentication, permission capping and audit logging are unchanged. Notifications get no reply; diagnostics go to stderr.- A
Dockerfilethat serves the bundled example project, with aseed_mcp_tokencommand that creates a token with a known value and sample data, so the server can be started without a host project.
Fixed¶
- Tool failures now set
isError: trueon thetools/callresult, as the MCP spec describes, so clients stop treating "not found", validation and permission errors as successes. The JSON text incontentis unchanged. A tool name that resolves to nothing (unknown operation, unregistered or unexposed model, nooperation_modelshape) is now a JSON-RPC-32602error naming the tool, instead of a result readingUnknown operation: no(#126)
Removed¶
- The example project's
run_mcp_servercommand, which imported a function the package no longer exports.
[0.10.1] - 2026-10-09¶
No code changes. This release updates what the package says about itself.
Added¶
- Django 5.1, 5.2 and 6.0 and Python 3.13 and 3.14 are tested in CI and declared in the package classifiers. The suite passed on them unchanged.
- A demo film in the README and on the docs landing page, rendered from
docs/media/render_demo.py. - A security policy with private vulnerability reporting, issue templates, and Dependabot for Actions and the uv lock.
Changed¶
- Dev tooling updated (ruff 0.16, mypy 2.4, django-stubs 6). The ruff formatter is kept out of Markdown code blocks.
[0.10.0] - 2026-10-05¶
This release closes the gaps found by driving every tool against a realistic admin. Several response and validation contracts change; read Changed before upgrading.
Fixed¶
update_*no longer wipes or rejectsDateTimeFieldvalues. The update path fedmodel_to_dict()output to the admin form as if it were POST data, which the admin's split date/time widget does not read: any update silently set optionalDateTimeFields toNone, and models with a required one (including the stockUserAdmin, viadate_joined) could not be updated at all. Updates, bulk updates, and inline updates now change only the fields the caller sent (#114)- Updates no longer fail with a data integrity error when a
JSONFieldholds{}or[](#114) DateTimeFields accept a single ISO 8601 string on create and update; previously only the widget's<field>_0/<field>_1keys worked, and only on create (#114)create_*andbulk_*create apply model defaults to omitted fields instead of reporting them as required, and fill omittedprepopulated_fieldstargets by slugifying their source fields (#115)save_related()andsave_formset()overrides now run: create, update, and bulk go through the admin'ssave_form→save_model→save_relatedpipeline, with inline rows saved through the admin's own formsets (#118)- Read-only checks use
get_readonly_fields(request, obj)rather than the barereadonly_fieldsattribute (#118) actions_*interpolates action descriptions ("Delete selected articles"instead of"Delete selected %(verbose_name_plural)s") (#119)
Added¶
- File uploads. A
FileField/ImageFieldvalue can be sent as{"filename": ..., "content_base64": ..., "content_type": ...}on create, update, bulk, and inline rows;nullclears an optional file. The decoded size is capped by the newMCP_UPLOAD_MAX_FILE_BYTESsetting (default 5 MiB), and the admin history records only the filename and size. Django'sDATA_UPLOAD_MAX_MEMORY_SIZEstill bounds the request body, so raise it to accept files above roughly 1.8 MB (#120) list_*filters reproduce the admin changelist. New lookups (iexact,startswith/endswithvariants,range,date,year,month,day); relation paths declared in the admin'slist_filterordate_hierarchy(for examplecustomer__is_staff); andSimpleListFiltersubclasses addressed by theirparameter_name.describe_*lists the usable filters and their choices underadmin_config.filters. Undeclared relation paths and hidden fields stay unfilterable (#116)- Computed admin values are returned under
_computed.get_*evaluates the non-field entries ofreadonly_fields, andlist_*those oflist_display, the way the admin does (#117) create_*acceptsinlines, with the same shape asupdate_*(#118)message_user()output is returned as amessageslist of{level, message}onaction_*,bulk_*, and successful create/update/delete. Setmcp_return_messages = Falseon a ModelAdmin to suppress it;MCPTokenAdmindoes, so a new token's plaintext is never returned over MCP (#119)
Changed¶
- Non-editable fields are now serialized.
auto_now/auto_now_addtimestamps,editable=Falsefields and the like appear in every serialized row, under the existingmcp_fields/mcp_exclude_fieldsrules. Review admins whose non-editable fields or computedlist_display/readonly_fieldsmethods expose data you do not want served, and add them tomcp_exclude_fields; a computed method that derives its value from a hidden field cannot be detected automatically (#117) - Parent and inline writes are atomic. Any inline validation, permission, or
min_num/max_numerror now rolls back the whole call and returns an error with"code": "inline_error"and the per-row details underinlines.errors. Previously the valid rows were saved and the response still saidsuccess: true(#118) - Input the form would ignore is rejected. Unknown, read-only, non-editable, and form-excluded keys return
Invalid field/Cannot set readonly fieldson create, update, and bulk instead of being dropped; malformed inline operations (unknown inline name,_deletewithoutid, a duplicated row id, stray keys) are errors too (#118) list_*validates filter values:inneeds a list,rangea two-item list,isnulla boolean (#116)tools/listoffers write tools only to tokens holding the matching permission:create_*needs add,update_*andaction_*change,delete_*delete, andbulk_*any of the three (#119)update_*accepts<field>_idforeign-key aliases, ascreate_*already did (#118)
[0.9.0] - 2026-10-04¶
Security¶
- Related models without an MCP admin are no longer served unchecked.
related_*andget_*withinclude_relatedpreviously returned every field of a related model that was not registered throughMCPAdminMixin(for example theUserbehind a foreign key, password hash included) to any token that could view the parent. Related models now answer to their admin's view permission, queryset scope, andfields/exclude— the MCP admin, or the default admin site's registration — and models with no admin at all are not served - Inline rows require view permission on the inline.
include_inlinesnow calls the inline's ownhas_view_permission(as the admin change page does) and serializes rows under the inline'sfields/exclude - Object-level permissions are enforced.
get_*,update_*,delete_*,bulk_*,related_*,history_*, anddelete_selectednow callhas_view/change/delete_permission(request, obj)with the target row, so admins that restrict access per object are honored - Deletes no longer cascade past the caller's permissions.
delete_*,bulk_*delete, anddelete_selectedrun the admin'sget_deleted_objects()check and refuse when the cascade reaches related objects the token may not delete, or protected objects - Hidden fields cannot be probed.
list_*filtersandorder_byaccept only MCP-visible fields (plus the primary key) and no reverse relations;autocomplete_*no longer falls back to searching hidden fields;related_*no longer serves a hidden forward relation; and values written to hidden fields are redacted from the admin history thathistory_*returns - Non-superusers manage only their own MCP tokens. In
MCPTokenAdmin(and therefore over MCP), a non-superuser sees, edits, and regenerates only tokens linked to their own user and can link a token only to themselves; previously MCPToken add/change permission was enough to mint or take over a token carrying another user's — including a superuser's — authority confirmation_datacan no longer override theaction,index,select_across, or_selected_actionfields of an admin action request- Inline
fields/exclude/readonly_fieldsnow also apply to inlines that declare a customform
[0.8.1] - 2026-09-29¶
Added¶
- Choice fields serialize with a
<field>_displaylabel sidecar. Every field defined withchoices(IntegerChoices,TextChoices, plain or grouped lists) keeps its raw stored value and gains a<field>_displaykey carrying the human-readable label ("status": 2, "status_display": "Active"), so MCP clients no longer need a schema round-trip to interpret enum values. Sidecars honormcp_fields/mcp_exclude_fieldsvisibility and never shadow a real model field of the same name (#113)
Fixed¶
describe_*now flattens grouped (optgroup) choices into individual value/label pairs; previously each group serialized as a single broken entry with the stringified inner list as its label (#113)
[0.8.0] - 2026-09-17¶
Added¶
MCP_ALLOW_URL_TOKENaccepts the bearer token as a URL path segment. Web MCP clients (claude.ai and ChatGPT custom connectors) register a plain URL and authenticate over OAuth, with no field for a staticAuthorizationheader, leaving them unable to reach the header route at all. With the setting enabled,POST <mount_point>/mcp_<key>.<secret>/authenticates the same token through the same pipeline; the route returns404while the setting is false (the default), and the header route is unaffected either way. The URL is now the credential — it reaches access logs and browser history — so use a dedicated, narrowly-scoped token for it
[0.7.2] - 2026-09-16¶
Changed¶
list_*rejects invalidfiltersandorder_byinstead of silently dropping them. Unknown fields, disallowed lookups, and relation traversal now return an error response naming every offending key; previously the query ran without those filters, handing the caller a success-shaped but unfiltered result (#111)
[0.7.1] - 2026-09-16¶
Fixed¶
describe_*(and any handler response) no longer crashes withPydanticSerializationErrorwhen admin config or model metadata contains Django lazy translation proxies —gettext_lazyfieldset names,verbose_names, and the like now serialize as their string value
Changed¶
- Minimum Pydantic version is now 2.7 (the log-redaction path already relied on a 2.7 feature; the floor now reflects reality)
[0.7.0] - 2026-09-15¶
Security¶
tools/listis filtered by the requesting token's permissions. Models failing thehas_module_permission/ view permission checks are skipped, mirroringfind_modelsandresources/list; a minimally-privileged token can no longer enumerate every exposed model's tool schemas (#101)- Fields hidden by
mcp_fields/mcp_exclude_fieldsdisappear from every schema surface. Tool descriptions,describe_*, and themodels://{model}/schemaresource previously listed the name, type, and constraints of deliberately hidden fields (password/token/PII columns); they now apply the same include/exclude resolution as serialization. Reverse relations stay discoverable forrelated_*under an include list (#102) - Bulk update redacts sensitive values in
LogEntrymessages.bulk_<model>withoperation: "update"wrote plaintext secrets intodjango_admin_logwhile the single-update path redacted them; both now share the same redacting serializer (which also drops the stray quote the old truncation branch appended) (#104) - Inline writes honor the inline admin's
fields,exclude, andreadonly_fields. The inline form is now resolved through the inline'sget_formset()like the Django admin, and keys targeting readonly or undeclared fields are rejected with the same error shapes as top-level update instead of being silently written (#105) MCPToken.has_perm/has_perms/has_module_permsare capped by the linked user's permissions. These public methods answered from the token's raw grants, bypassing the 0.5.0 cap rule that MCP requests already enforce; they now answer fromget_effective_permissions(), matching theTokenUserproxy.get_all_permissions()remains raw-grant introspection and is documented as such (#109)
Fixed¶
- Admin hooks calling
self.message_user()insave_model/delete_model/actions no longer crash MCP writes withMessageFailure: the synthetic MCP requests now carry an in-memory messages storage. This also un-breaks thecreate_mcptokentool, which could never succeed (#100) search_fieldsoperator prefixes (^,=,@) andfield__lookupforms no longer breaklist_*search andautocomplete_*: searching goes throughModelAdmin.get_search_results(), so custom overrides are honored too (#103)related_*on a null forward FK/O2O returns{type: "single", result: null}instead of the undocumentedvaluebranch stringifyingNone, and an empty reverse one-to-one returns the same null result instead of "An internal error occurred" (#106)- Grouped (tupled) entries in the admin's
fields— e.g.fields = [("name", "email")]— no longer makeget_*/list_*return empty objects; include/exclude lists are flattened before use (#107) - Input-validation gaps: a legitimate
pk=0is looked up instead of rejected as missing;bulk_*with a non-listitemsreturns{"error": "items must be a list"}instead of a success-shaped no-op;history_*honors theoffsetit accepts (#110)
Changed¶
- JSON-RPC notifications never receive a response body: the whole
notifications/namespace (e.g.notifications/cancelled,notifications/roots/list_changed) and any request without anidreturn an empty HTTP 202, per JSON-RPC 2.0. Unknown request methods with anidkeep the-32601error envelope (#108)
[0.6.0] - 2026-09-15¶
Security¶
- All row lookups now honor
ModelAdmin.get_queryset()scoping.update_*,delete_*,bulk_*,related_*,history_*, andautocomplete_*previously usedmodel.objectsdirectly, so rows hidden from the admin changelist (multi-tenant filters, soft-delete, proxy scoping) could still be read, updated, or deleted by pk (#88) mcp_expose = Falsemodels are no longer callable. Tools for non-exposed models were hidden fromtools/listbut executed when called by name; they now return the same "Model not found" error as unregistered models (#89)related_*only serves actual relations. Any attribute name (plain fields, properties, methods) was previously returned as a string value, bypassingmcp_fields/mcp_exclude_fields; non-relation names are now rejected (#90)- Related and inline reads check permissions on the related model.
related_*returnspermission_deniedandinclude_related/include_inlinesomit models the token may not view; related rows also come from the related admin's queryset scope (#91) - Inline updates and deletes are scoped to the parent object. Inline items in
update_*were looked up by pk alone, allowing any row of the inline model to be modified or deleted through an unrelated parent (#92) - Admin token regeneration requires POST and change permission. The regenerate view previously invalidated and reissued credentials on a plain GET (CSRF-able) and admitted any active staff user regardless of MCPToken permissions (#96)
Fixed¶
get_*withinclude_related: trueno longer fails with "An internal error occurred" on models that have a forward ForeignKey (#93)- Negative or non-integer
limit/offsetinrelated_*,history_*, andautocomplete_*now return a JSON validation error instead of an unhandled HTTP 500; these handlers also honor theMCP_MAX_LIST_LIMITcap, andcall_toolgained a last-resort sanitized-error guard (#94) - Bulk and action paths follow the standard admin pipeline:
delete_selectedwritesLogEntryrecords and callsdelete_queryset(); bulk create/update go throughsave_model()and apply the same unknown-field/readonly guards as single-object update; bulk delete callsdelete_model()(#95) - A cross-app model name collision in the MCP registry is now logged instead of silently dropping the second model's registration (#99)
Changed¶
- The JSON-RPC endpoint returns spec-compliant error envelopes: parse errors (
-32700), unknown methods (-32601), and invalid params (-32602, sanitized details inerror.data) come back with HTTP 200 instead of bare 400 bodies; tool-result failures return their envelope with 200 instead of 500;notifications/initializedreturns an empty HTTP 202 (#97) MCPToken.last_used_atwrites are throttled to once perMCP_LAST_USED_RESOLUTIONseconds (default 60; set 0 to record every use) instead of every authenticated request (#98)
[0.5.0] - 2026-09-15¶
Changed — BREAKING¶
- Token-level permissions are now enforced. Authorization answers from the token's effective permissions — its own
permissionsandgroupsfields intersected with the linked user's Django permissions — via a permission proxy placed onrequest.user. A token can narrow its user's access but never exceed it: a token with no grants has no access even when bound to a superuser, a grant the linked user lacks stays ineffective, and deactivating the linked user disables the token's access. The linked user remains the audit identity forLogEntryrecords. Upgrade note: existing tokens had access equal to their user's permissions; after upgrading they must also be granted the needed permissions/groups on the token itself, or their requests will be denied. - Leaving Expires At blank in the admin form now creates a token that never expires, matching the field's help text. Programmatic creation without an
expires_atkwarg still defaults to 90 days.
Added¶
MCPToken.get_effective_permissions()— the token's grants capped by the linked user's permissions (what requests actually authorize with)MCPToken.has_module_perms(app_label)— module-level permission check mirroring Django'sUser.has_module_perms, used byfind_modelsdiscoveryTokenUserpermission proxy (django_admin_mcp.models.TokenUser) answering Django's permission API from the token's effective permissions while delegating identity attributes to the linked user
Fixed¶
find_modelsnow reportstools_exposedbased on each admin'smcp_exposeflag instead of alwaystrue- The advertised
autocomplete_*limit default now matches the handler default (10, was 20 in the schema) - The generated
list_*tool description now advertises the full filter-lookup whitelist (contains,gt, andltwere missing)
Documentation¶
- Documentation audited against the code: corrected request/response shapes (JSON-RPC envelope,
params-nestedtools/call), error payloads, permission semantics (checks run against the token's linked user), serialization details, and settings reference (MCP_MAX_LIST_LIMIT,MCP_ACTION_MAX_FILE_BYTES); documented the action confirmation flow, file downloads, inline editing, and queryset scoping
[0.4.0] - 2026-09-15¶
Added¶
- MCP Prompts support:
prompts/listandprompts/getserve workflow guides (explore_models,understand_model,crud_guide,bulk_operations_guide) (#65) - MCP Resources support:
resources/list,resources/templates/list, andresources/readexpose model schemas (models://<model>/schema) and instance data (data://<model>/,data://<model>/<id>), permission-filtered (#66) - Two-step confirmation workflow for admin actions: actions returning an HTML page report
requires_confirmation: true; re-calling withconfirm: true(plus optionalconfirmation_data) executes them. Actions also receive Django's standard POST fields (action,_selected_action) (#63) min_num/max_numinline constraints are enforced when editing inlines viaupdate_<model>(#61, #62)
Changed¶
find_modelsrespectsModelAdmin.has_module_permission(): hidden modules are excluded from discovery (#64)list_<model>validateslimit/offsetand caps page size atMCP_MAX_LIST_LIMIT(default 1000) (#47)- The two HTTP view code paths now share one auth/parse/validate/execute pipeline (#43)
[0.3.3] - 2026-09-15¶
Added¶
mcp_use_admin_querysetoption (defaultTrue): list/get and admin actions now start fromModelAdmin.get_queryset(request), so proxy models, soft-delete, and multi-tenant scoping match the admin changelist (#84, #85)- Admin action
HttpResponse/StreamingHttpResponsedownloads are returned as structured file payloads (UTF-8 or base64) instead ofstr(response), with a size cap viaMCP_ACTION_MAX_FILE_BYTES(default 5 MiB) (#86) - MCP Inspector troubleshooting guide for Bearer token setup (#81)
Fixed¶
FileField/ImageFieldvalues serialize as storage-path strings; empty image fields no longer crashlist_*responses (#87)describe_*no longer crashes whenModelAdmin.orderingisNone(the Django default); filter classes and callables in admin config serialize as dotted paths (#83)- The MCP
initializeresponse now reports the real package version instead of a hardcoded one
Security¶
- Filter lookups are restricted to a whitelist (
exact,contains,icontains,gt,gte,lt,lte,in,isnull) on direct fields only — relation traversal and regex lookups are rejected (#40) - Sensitive values (passwords, tokens, secrets) are redacted from admin
LogEntryaudit messages (#42) mcp_exclude_fieldsis now applied on list and related serialization, not just get/create/update (#82)delete_selectedchecks delete permission before any ID lookup to avoid leaking row existence (#85)
[0.3.2] - 2026-07-09¶
Changed¶
- License changed from GPL-3.0 to MIT
[0.3.1] - 2026-03-12¶
Changed¶
- CRUD handlers use
ModelAdmin.save_model()anddelete_model()for the standard Django admin pipeline (#74)
Fixed¶
- M2M fields serialize as lists of PKs in list/get responses (#77)
[0.3.0] - 2026-02-08¶
Added¶
non_atomic_requestsdecorator to async views forATOMIC_REQUESTScompatibility (#72)require_registered_modelandrequire_permissiondecorators for handler authorization- Comprehensive MkDocs Material documentation with getting started guides, tool reference, and example conversations
Changed¶
- Use Django's
get_actions()to resolve admin actions for listing and execution (#73) - Replace
jsonmodule with PydanticTypeAdapteracross all handlers (#53, #54, #55, #56) - Wrap CRUD and bulk operations in
transaction.atomic()for data integrity (#57) - Apply
require_registered_modelandrequire_permissiondecorators to CRUD, relations, and meta handlers - Narrow broad exception handling in
authenticate_token
Fixed¶
- URL path duplication when mounting at custom path (e.g.,
path("mcp/", ...)produced/mcp/mcp/) (#68, #71)
Security¶
- Sanitize error responses to prevent internal detail leakage (#70)
- Add permission checks to
handle_history(),handle_related(),handle_autocomplete(),handle_describe(), andhandle_find_models() - Inline permission checks to prevent privilege escalation
- Add field filtering to
serialize_instance()to prevent sensitive data exposure (#58)
[0.2.1] - 2025¶
Changed¶
- Restrict model lookups to MCPAdminMixin registry only
- Remove redundant
str()calls in_get_action_info
[0.2.0] - 2025¶
Added¶
- Hashed token authentication with
mcp_<key>.<secret>format - O(1) token lookup via indexed
token_keyfield - Constant-time secret comparison to prevent timing attacks
require_registered_modelandrequire_permissiondecorators- Bulk create support (
handle_bulk_create) mcp_fieldsandmcp_exclude_fieldsfor field filtering
Changed¶
- Split
handle_bulkintohandle_bulk_create,handle_bulk_update,handle_bulk_delete - Extracted permission decorators to
handlers/decorators.py
Security¶
- Token secret is now hashed with per-token salt (SHA-256)
- Token format changed to
mcp_<key>.<secret>for structured authentication
[0.1.0] - 2024-01-15¶
Added¶
- Initial release
MCPAdminMixinfor exposing Django admin models- Token-based authentication with
MCPTokenmodel - CRUD operations:
list_*,get_*,create_*,update_*,delete_* - Model introspection:
describe_*,find_models - Admin actions:
actions_*,action_*,bulk_* - Relationships:
related_*,history_*,autocomplete_* - Full Django admin permission integration
- Support for Django 3.2, 4.0, 4.1, 4.2, 5.0
- Support for Python 3.10, 3.11, 3.12
Security¶
- Bearer token authentication
- Token expiration (default 90 days)
- Django permission checking on all operations
- Principle of least privilege (tokens start with no permissions)
Version History¶
| Version | Python | Django |
|---|---|---|
| 0.7.2 | 3.10+ | 3.2+ |
| 0.7.1 | 3.10+ | 3.2+ |
| 0.7.0 | 3.10+ | 3.2+ |
| 0.6.0 | 3.10+ | 3.2+ |
| 0.5.0 | 3.10+ | 3.2+ |
| 0.4.0 | 3.10+ | 3.2+ |
| 0.3.x | 3.10+ | 3.2+ |
| 0.2.x | 3.10+ | 3.2+ |
| 0.1.0 | 3.10+ | 3.2+ |
Upgrade Guide¶
From 0.6.x to 0.7.0¶
No migrations. Behavior changes to review:
tools/listis now permission-filtered. Tools appear only for models the token holds view (and module) permission on, matchingfind_models. Clients that enumerated all tools with a low-privilege token will see a shorter list; grant view permissions for models that should stay discoverable.- Hidden fields left every schema surface. Fields excluded via
mcp_fields/mcp_exclude_fieldsno longer appear in tool descriptions,describe_*, ormodels://{model}/schema. Clients introspecting those fields' metadata must expose them deliberately. MCPToken.has_perm/has_perms/has_module_permsnow answer from effective permissions (grants capped by the linked user). Downstream code that used them for raw-grant introspection should useget_all_permissions()instead.- Inline writes are validated like the admin. Inline items targeting fields that are readonly or not declared on the inline now return errors instead of writing. Clients depending on the old behavior must update the inline's
fields/readonly_fields. - Notifications get no response body. Any JSON-RPC request without an
id(including all ofnotifications/*) returns an empty HTTP 202; only requests with anidreceive envelopes. related_*null relations changed shape. Empty forward FK/O2O and reverse O2O now return{"type": "single", "result": null}instead of avaluestring or an internal error.
From 0.5.x to 0.6.0¶
No migrations. Behavior changes to review:
mcp_expose = Falsemodels are no longer callable. If any client relied on calling tools for a registered-but-not-exposed model, setmcp_expose = Trueon that admin.- Row scoping now applies everywhere.
update_*,delete_*,bulk_*,related_*,history_*, andautocomplete_*honorModelAdmin.get_queryset(request); rows outside the admin queryset now return "not found". related_*no longer returns plain field values. Only actual relations are served; clients reading non-relation attributes through it must useget_*instead.- Related/inline reads require view permission on the related model. Grant the token
viewpermission on inline/related models it should keep seeing throughinclude_inlines/include_related/related_*. - JSON-RPC error responses changed shape. Parse errors, unknown methods, and invalid params now arrive as JSON-RPC error envelopes (
-32700/-32601/-32602) with HTTP 200, andnotifications/initializedreturns an empty HTTP 202. Clients checking for HTTP 400/500 on these paths must readerror.codeinstead. MCPToken.last_used_atnow updates at most once perMCP_LAST_USED_RESOLUTIONseconds (default 60). Set the setting to0to restore per-request writes.
From 0.4.x to 0.5.0¶
Authorization changed from the linked user's permissions to the token's own permissions (capped by the user's). Before or immediately after upgrading:
-
Update the package and run migrations:
-
Grant each existing token the permissions or groups it needs (in the MCP Token admin, or via
token.permissions/token.groups). Tokens without grants are denied every operation, regardless of their user's permissions — including superusers. -
Optionally revisit
expires_at: blank in the admin form now means "never expires" instead of the 90-day default.
From 0.1.x to 0.2.x¶
Token format has changed. You must:
-
Update the package:
-
Run migrations:
-
Recreate all tokens (token format changed to
mcp_<key>.<secret>)
From Pre-release to 0.1.0¶
If you were using a pre-release version:
-
Update the package:
-
Run migrations:
-
Recreate any tokens (token format may have changed)
Deprecation Policy¶
- Features are deprecated for at least one minor version before removal
- Deprecated features will emit warnings
- Migration guides are provided for breaking changes