django-mcp-sql

Purpose: Enabling secure, read-only SQL access for LLM agents via the MCP protocol.

Inferred · not functionally tested

Audience: developers building agent-based data access systems

Inferred · not functionally tested

Functions: rag, data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, django-mcp-sql takes a focused approach. Inferred · not functionally tested: It focuses on enabling secure, read-only SQL access for LLM agents via the MCP protocol. Inferred · not functionally tested: It is built as an open-source project for developers building agent-based data access systems. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It runs on the command line and API, and it can be self-hosted.

It is developed by thepapermen, and it first shipped in 2026. Development happens publicly on GitHub with 26 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are Read-only SQL interface, postgreSQL support, and MCP protocol. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.