Generic, schema-driven MCP server for drf-react-by-schema projects.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"drf-react-by-schema-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
.. image:: https://gitlab.com/eita/drf-react-by-schema/drf-react-by-schema-mcp/-/raw/master/banner_drf-react-by-schema-mcp_2171x345.png :width: 1280 :alt: DRF And React By Schema - MCP DRF And React By Schema - MCP ============================= A generic, **schema-driven MCP server** for projects built with **DRF And React By Schema (DRBS)**. It exposes any DRBS project's DRF API (``/api/...``) to MCP clients such as `opencode <https://opencode.ai>`_ through a small set of generic tools — ``consultar``, ``resumo``, ``criar``, ``editar``, ``minha_conta`` — plus the schema-aware ``knowledge``/``guia`` tools and optional per-project shortcuts, so an assistant can **understand** the project (models, fields, endpoints, conventions, reverse relations) and then read (and, when opted in, write) its data with **no per-model tool explosion**. The server is a **stateless proxy**: it takes the caller's OAuth 2.1 Bearer token (issued by `drf-react-by-schema-oauth <https://pypi.org/project/drf-react-by-schema-oauth/>`_), forwards it to the project's ``/api/...`` and lets the project's **own DRF permissions** scope the data. It stores **no credentials**. About the suite --------------- *drf-react-by-schema* is a suite that builds headless Django + React applications directly from your models: * **drf-react-by-schema-django** (`PyPI <https://pypi.org/project/drf-react-by-schema/>`_) — generates the DRF API (serializers, viewsets, filters, schemas) from your models; * **drf-react-by-schema-react** (`npm <https://www.npmjs.com/package/drf-react-by-schema>`_) — consumes those schemas to build the React forms, grids and CRUD interfaces; * **drf-react-by-schema-oauth** — OAuth 2.1 **authorization/resource server** that issues the tokens both the API and this MCP server accept; * **drf-react-by-schema-mcp** (this package) — the generic **MCP server** that exposes the same API to MCP clients. About this package ------------------ A DRBS project already exposes a ri…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.