django-telescope — Claude Code MCP server: features and setup
This MCP server gives an AI assistant ways to inspect a Django project, including its models, database schema, settings, and logs. Use it when an agent needs project context.
claude mcp add django-telescope -e DJANGO_SETTINGS_MODULE=<DJANGO_SETTINGS_MODULE> -- uvx django-telescopeWhat django-telescope does
The server exposes tools for inspecting a Django codebase. An assistant can list models, URLs, and management commands, examine database schema and migrations, query settings by dotted path, and read filtered application logs. Its tools are read-only, so they don’t alter project data.
To start it, provide Django’s settings module through DJANGO_SETTINGS_MODULE or the --settings option. The default transport is stdio; use SSE for network access. Production deployments using SSE require a Bearer token, while stdio has no authentication. That distinction matters if the server will be reachable remotely.
For Claude Code, add the server with claude mcp add and run it through uvx. Configuration examples are also provided for Codex, Cursor, and other MCP clients. Set the settings module to the one used by your Django project before connecting.
What it helps with
- inspect models and management commands in a Django project
- review database schema, migrations, and relationships
- look up a Django setting by its dotted path
- read filtered application logs
Example prompts for the agent
- List the models and management commands in my Django project.
- Check the database schema and show related models.
- Look up the database setting and read recent application logs.
How to install django-telescope
Platform CLI
claude mcp add django-telescope -e DJANGO_SETTINGS_MODULE=<DJANGO_SETTINGS_MODULE> -- uvx django-telescopeReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from django-telescope <command>
Platform CLI
codex mcp add django-telescope --env DJANGO_SETTINGS_MODULE=<DJANGO_SETTINGS_MODULE> -- uvx django-telescopeReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from django-telescope <command>
Config file
{
"mcpServers": {
"django-telescope": {
"command": "uvx",
"args": [
"django-telescope"
],
"env": {
"DJANGO_SETTINGS_MODULE": "<DJANGO_SETTINGS_MODULE>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from django-telescope <command>
Config file
{
"servers": {
"django-telescope": {
"type": "stdio",
"command": "uvx",
"args": [
"django-telescope"
],
"env": {
"DJANGO_SETTINGS_MODULE": "<DJANGO_SETTINGS_MODULE>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from django-telescope <command>
Platform CLI
gemini mcp add -e DJANGO_SETTINGS_MODULE=<DJANGO_SETTINGS_MODULE> django-telescope uvx django-telescopeReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from django-telescope <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about django-telescope
How do I install django-telescope in Claude Code?
Run claude mcp add django-telescope -e DJANGO_SETTINGS_MODULE=<DJANGO_SETTINGS_MODULE> -- uvx django-telescope. Replace the placeholder with your Django project’s settings module.
What does django-telescope do?
It gives an MCP client read-only tools to inspect Django models, URLs, management commands, database structure, settings, and application logs.
Does the server require an authentication token?
SSE in production requires a Bearer token. The stdio transport does not provide authentication.
