A
licenseNot graded
qualityD
maintenanceProvides read-only access to Django admin data over MCP, scoped to the signed-in staff user's permissions and respecting all ModelAdmin-level controls.
MIT
django-admin-mcp
by 7tg
Related Servers
Alternatives to django-admin-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes Django admin's ModelAdmin as MCP tools, with identical permissions, form validation, and session authentication.204 PyPI5MIT
- AlicenseNot gradedqualityDmaintenanceAutomatically exposes Django REST Framework endpoints as MCP tools with zero configuration, supporting multiple transports and authentication.MIT
- AlicenseNot gradedqualityCmaintenanceExposes Django REST Framework APIs as MCP tools for AI agents via the Model Context Protocol, with automatic discovery and security.17 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceTurns Django models into MCP tools and a REST API from a single class, and can generate a Django project from a MySQL or Postgres schema.2MIT
- AlicenseNot gradedqualityCmaintenanceExposes Django REST Framework API documentation via MCP for AI coding agents to read, understand, and write frontend integration code.16MIT
TDQS
A3.5/5.0
Scored across 37 tools
Disambiguation4/5
Tools are namespaced by model (mcptoken vs author vs article), so cross-model confusion is minimal. However, within a model there is mild overlap: list_X vs autocomplete_X both search, and bulk_X competes with the individual create/update/delete tools. Descriptions do help disambiguate these, keeping it above mediocre.
Naming Consistency4/5
The convention is highly predictable: verb_model (list_author, get_article, create_mcptoken, bulk_author, related_article), giving a consistent verb_noun pattern. The only deviation is the generic find_models discovery tool, and the subtle actions_X/action_X pairing, which are minor blemishes.
Tool Count3/5
37 tools is heavy, exceeding the 25+ threshold flagged as excessive. The count is systematic (12 near-identical tools per each of three models plus find_models), so it is defensible for a generic multi-model admin surface, but it is still unwieldy for an agent to navigate.
Completeness5/5
Each model gets a full lifecycle: list, get, create, update, delete, describe, actions/action, bulk, related, history, and autocomplete. With find_models for discovery and no obvious missing operation, the surface is exhaustive for Django admin management.
Maintenance
ActivityActive
ResponsivenessWithin a week