bazis-mcp

The MCP server of a Bazis project. It gives AI agents (Claude Code, IDEs with MCP support) what they need to build and check a Bazis project from the project itself rather than from memory:

• the catalog of the Bazis packages, also the ones not installed: what each one solves, what it requires, and its guide for agents (AGENTS.md and bazis_manifest.toml);
• the facts about the project: installed packages, settings (secrets hidden), models and routes (bazis.core.introspect);
• the system checks of the project and of its Bazis packages (manage.py bazis_doctor).

All tools only read. The agent changes the files itself and checks the result with the server.

Installation

Install it as a development dependency of the project:

pip install bazis-mcp

Register the server for the MCP client with the directory of manage.py (MCP clients start servers in their own working directory, usually the repository root):

# Claude Code, run in the repository root
claude mcp add bazis -- .venv/bin/bazis-mcp --project-dir app

or in .mcp.json of the repository:

{
  "mcpServers": {
    "bazis": {"command": ".venv/bin/bazis-mcp", "args": ["--project-dir", "app"]}
  }
}

(app is the directory of manage.py; leave --project-dir out if it is the root.)

bazis-mcp [--project-dir DIR] [--settings MODULE]:

• --project-dir — the directory of manage.py and project.env (default: the current directory);
• --settings — the settings module (default: DJANGO_SETTINGS_MODULE, or the module that manage.py sets).

The environment of the project (project.env, BS_* variables) is read as by manage.py. The server needs neither the database nor Redis. It loads the settings and the application of the project, so it runs the project code like manage.py does. If the project cannot be loaded, the catalog tools still work and the project tools return the error.

bazis-mcp is not a Django app: do not add it to BS_INSTALLED_APPS.

Tools

Resource: bazis://packages/{name}/agents.md. Prompts: add_package(name) (add a package and make the checks pass) and audit_project (review the project against the guides and checks of its packages).

An installed package is described by its installed files. The packages that are not installed, and those installed in a version without a guide (before 2.4), come from catalog.json, a snapshot of the latest releases taken at the release of bazis-mcp; guide_version is the version the guide describes.

The settings are shown with the secrets hidden by bazis.core.introspect (by the names of the settings and keys, the passwords of URLs and the credentials of Authorization values). The tool results go to the model of the MCP client: review what the project keeps in its settings before connecting it.