django-admin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_modelsA | Discover available Django models registered with MCP. Use this to find which models have tools available. |
| list_mcptokenA | List MCP Token instances with filtering, searching, ordering, and pagination. Filter lookups: field (exact), field__iexact, field__contains, field__icontains, field__startswith, field__istartswith, field__endswith, field__iendswith, field__gt, field__gte, field__lt, field__lte, field__in, field__range, field__isnull; date fields also take field__year, field__month, field__day (and field__date on datetimes), optionally followed by a comparison (field__year__gte). Relation paths (e.g. category__slug) and custom filter parameters work only when the admin declares them in list_filter / date_hierarchy: describe_mcptoken lists them under admin_config.filters. Invalid filters return an error. Available fields:
|
| get_mcptokenB | Get a specific MCP Token by ID with optional inline and related data. |
| create_mcptokenA | Create a new MCP Token, optionally with inline rows. Date and datetime fields take a single ISO 8601 string (e.g. '2026-03-01' or '2026-03-01T09:30:00Z'). Foreign keys take the related object's ID, many-to-many fields a list of IDs. A field the admin form does not accept (unknown, read-only or non-editable) is rejected with an error, never ignored. Fields:
|
| update_mcptokenA | Update an existing MCP Token with optional inline updates. Only the fields sent are changed. Date and datetime fields take a single ISO 8601 string (e.g. '2026-03-01' or '2026-03-01T09:30:00Z'). Foreign keys take the related object's ID, many-to-many fields a list of IDs. A field the admin form does not accept (unknown, read-only or non-editable) is rejected with an error, never ignored. Fields:
|
| delete_mcptokenC | Delete a MCP Token by ID |
| describe_mcptokenA | Get detailed metadata about the MCP Token model including field definitions, relationships, and admin configuration. |
| actions_mcptokenA | List available admin actions for MCP Token. Returns action names and descriptions that can be executed via action_mcptoken. |
| action_mcptokenA | Execute an admin action on selected MCP Token instances. Use actions_mcptoken to discover available actions. |
| bulk_mcptokenA | Perform bulk operations on MCP Token: create, update, or delete multiple items. For 'create': items is a list of data objects For 'update': items is a list of {id, data} objects For 'delete': items is a list of IDs |
| related_mcptokenA | Fetch related objects for a MCP Token instance. Use describe_mcptoken to discover available relations. |
| history_mcptokenA | Get the change history (LogEntry records) for a MCP Token instance. Shows who made what changes and when. |
| autocomplete_mcptokenA | Search MCP Token instances for autocomplete suggestions. Useful for populating FK/M2M field widgets. |
| list_authorA | List Author instances with filtering, searching, ordering, and pagination. Filter lookups: field (exact), field__iexact, field__contains, field__icontains, field__startswith, field__istartswith, field__endswith, field__iendswith, field__gt, field__gte, field__lt, field__lte, field__in, field__range, field__isnull; date fields also take field__year, field__month, field__day (and field__date on datetimes), optionally followed by a comparison (field__year__gte). Relation paths (e.g. category__slug) and custom filter parameters work only when the admin declares them in list_filter / date_hierarchy: describe_author lists them under admin_config.filters. Invalid filters return an error. Available fields:
|
| get_authorB | Get a specific Author by ID with optional inline and related data. |
| create_authorA | Create a new Author, optionally with inline rows. Date and datetime fields take a single ISO 8601 string (e.g. '2026-03-01' or '2026-03-01T09:30:00Z'). Foreign keys take the related object's ID, many-to-many fields a list of IDs. A field the admin form does not accept (unknown, read-only or non-editable) is rejected with an error, never ignored. Fields:
|
| update_authorA | Update an existing Author with optional inline updates. Only the fields sent are changed. Date and datetime fields take a single ISO 8601 string (e.g. '2026-03-01' or '2026-03-01T09:30:00Z'). Foreign keys take the related object's ID, many-to-many fields a list of IDs. A field the admin form does not accept (unknown, read-only or non-editable) is rejected with an error, never ignored. Fields:
|
| delete_authorC | Delete a Author by ID |
| describe_authorA | Get detailed metadata about the Author model including field definitions, relationships, and admin configuration. |
| actions_authorA | List available admin actions for Author. Returns action names and descriptions that can be executed via action_author. |
| action_authorA | Execute an admin action on selected Author instances. Use actions_author to discover available actions. |
| bulk_authorA | Perform bulk operations on Author: create, update, or delete multiple items. For 'create': items is a list of data objects For 'update': items is a list of {id, data} objects For 'delete': items is a list of IDs |
| related_authorA | Fetch related objects for a Author instance. Use describe_author to discover available relations. |
| history_authorB | Get the change history (LogEntry records) for a Author instance. Shows who made what changes and when. |
| autocomplete_authorA | Search Author instances for autocomplete suggestions. Useful for populating FK/M2M field widgets. |
| list_articleA | List Article instances with filtering, searching, ordering, and pagination. Filter lookups: field (exact), field__iexact, field__contains, field__icontains, field__startswith, field__istartswith, field__endswith, field__iendswith, field__gt, field__gte, field__lt, field__lte, field__in, field__range, field__isnull; date fields also take field__year, field__month, field__day (and field__date on datetimes), optionally followed by a comparison (field__year__gte). Relation paths (e.g. category__slug) and custom filter parameters work only when the admin declares them in list_filter / date_hierarchy: describe_article lists them under admin_config.filters. Invalid filters return an error. Available fields:
|
| get_articleB | Get a specific Article by ID with optional inline and related data. |
| create_articleA | Create a new Article, optionally with inline rows. Date and datetime fields take a single ISO 8601 string (e.g. '2026-03-01' or '2026-03-01T09:30:00Z'). Foreign keys take the related object's ID, many-to-many fields a list of IDs. A field the admin form does not accept (unknown, read-only or non-editable) is rejected with an error, never ignored. Fields:
|
| update_articleA | Update an existing Article with optional inline updates. Only the fields sent are changed. Date and datetime fields take a single ISO 8601 string (e.g. '2026-03-01' or '2026-03-01T09:30:00Z'). Foreign keys take the related object's ID, many-to-many fields a list of IDs. A field the admin form does not accept (unknown, read-only or non-editable) is rejected with an error, never ignored. Fields:
|
| delete_articleC | Delete a Article by ID |
| describe_articleA | Get detailed metadata about the Article model including field definitions, relationships, and admin configuration. |
| actions_articleA | List available admin actions for Article. Returns action names and descriptions that can be executed via action_article. |
| action_articleA | Execute an admin action on selected Article instances. Use actions_article to discover available actions. |
| bulk_articleB | Perform bulk operations on Article: create, update, or delete multiple items. For 'create': items is a list of data objects For 'update': items is a list of {id, data} objects For 'delete': items is a list of IDs |
| related_articleA | Fetch related objects for a Article instance. Use describe_article to discover available relations. |
| history_articleA | Get the change history (LogEntry records) for a Article instance. Shows who made what changes and when. |
| autocomplete_articleB | Search Article instances for autocomplete suggestions. Useful for populating FK/M2M field widgets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explore_models | Guide for discovering the Django admin models exposed over MCP |
| understand_model | Deep dive into a specific model's fields, constraints, and admin config |
| crud_guide | Best practices for creating, updating, and deleting objects of a model |
| bulk_operations_guide | How to efficiently perform bulk operations and admin actions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mcptoken schema | Field metadata and admin configuration for mcptoken |
| mcptoken data | Paginated list of mcptoken instances (first 50) |
| author schema | Field metadata and admin configuration for author |
| author data | Paginated list of author instances (first 50) |
| article schema | Field metadata and admin configuration for article |
| article data | Paginated list of article instances (first 50) |
TDQS
Scored across 37 tools
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.
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.
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.
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.