Django MCP server
{
"mcpServers": {
"frisian-mcp-django": {
"type": "http",
"url": "https://mcp.frisian-mcp.com/mcp/"
}
}
}{
"mcpServers": {
"frisian-mcp-django": {
"type": "http",
"url": "https://mcp.frisian-mcp.com/mcp/"
}
}
}{
"mcpServers": {
"frisian-mcp-django": {
"type": "http",
"url": "https://mcp.frisian-mcp.com/mcp/"
}
}
}{
"servers": {
"frisian-mcp-django": {
"type": "http",
"url": "https://mcp.frisian-mcp.com/mcp/"
}
}
}{
"mcpServers": {
"frisian-mcp-django": {
"type": "http",
"url": "https://mcp.frisian-mcp.com/mcp/"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.12
What it does
frisian-mcp exposes Django REST Framework ViewSets as Model Context Protocol tools, automatically discovering and bundling API endpoints into dispatchers. It is designed for developers building AI agents that need to interact with Django APIs while minimizing token consumption.
- Connect an AI agent to a Django REST Framework API and call ViewSet actions through MCP without writing custom tool definitions.
- Reduce agent context window usage by grouping multiple API endpoints into single dispatcher tools, saving 95–99% of tokens in tools/list responses.
- Scope API access per agent credential using OAuth 2.0 or static tokens, with per-action validation and host-app permission enforcement.
Tools this server exposes
| Tool | Does |
|---|---|
| dispatcher | Groups multiple ViewSet actions into a single tool with an action parameter; includes built-in help mode for discovery. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.