# Choose modules for a purpose

> You do not have to take everything: six common purposes and the modules that suffice.


Every module can be taken on its own. The table names the smallest set for six common purposes; the page per module is in this section, the state on the infrastructure page.

## Purposes {#zwecke}

| I want to … | Modules |
|---|---|
| only validate manifests | [Registry standard](module-registry-standard.md) |
| read the directory | Registry standard + [API spine](module-api-spine.md) |
| check entries myself | [Checker](module-checker.md) + Registry standard |
| query federal law via MCP | [MCP gateway](module-mcp-gateway.md) + [fedlex engine](module-fedlex-engine.md) |
| query political data via MCP | MCP gateway + [Political data engine](module-political-data-engine.md) |
| address the platform as an agent | [A2A agent](module-a2a-agent.md) + API spine + MCP gateway |

## Dependencies {#abhaengigkeiten}

Which module needs which is shown by the dependency figure on the [infrastructure page](dependencies.md). If you want everything, take [All at once](all-at-once.md).

---

Source: docs/en/infrastructure/compose-modules.md