bazis-mcp

# bazis-mcp The [MCP](https://modelcontextprotocol.io) server of a [Bazis](https://github.com/ecofuture-tech/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`), from bazis 2.13 also those against its database; - its frontend layer made by bazis-front: the issues of the specs, what is stale and the components that can be added (`manage.py bazis_front`); - the programs a project needs on this machine (Python, uv, Node.js, PostgreSQL, Redis, GDAL, gettext) and their installation with the package manager, once the user agrees; - a new project created from the conversation (the skeleton, `.venv`, the database), or an existing one chosen, with the rules of Bazis for the agent and its task; - for a client without a shell or files of its own: the files of the project, its commands from a closed table, its servers and its Bazis packages. The tools only read, but `create_project`, which writes a new project, `use_project`, which chooses the project of the next calls, `install_tools`, which installs programs of the machine, and the tools of the project: `add_packages`, `run_command`, `start_server`, `stop_server`, `write_file`, `delete_file` and `clean_project`. They never run a command of the caller: the commands come from closed tables, as argv without a shell, and the files stay in the project directory. ## Create an app from Claude Connect the server once; there is nothing to configure and no Bazis to install by hand. ```bash # Claude Code claude mcp add bazi…