# Installer mcap avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de mcap pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:mcap
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install mcap
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:mcap
- **Gestionnaire de paquets:** Homebrew
- **Version:** 0.3.0
- **Résumé source:** Serialization-agnostic container file format for pub/sub messages
- **Page d'accueil:** <https://mcap.dev>
- **Dépôt:** <https://github.com/foxglove/mcap>
- **Dernière mise à jour:** 2026-07-15T09:44:52Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- mcap (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 0.3.0
## Historique du projet et usages

MCAP is an open file format and command-line tool for recording, inspecting, and converting publish/subscribe message logs. It is serialization-agnostic, which lets robotics and telemetry systems store ROS, Protobuf, JSON, and other message encodings in one container format.

### Historique du projet

Foxglove's official documentation presents MCAP as a container format for pub/sub messages with a formal specification, language libraries, and a CLI. The GitHub release history shows the mcap-cli release stream beginning publicly in 2022, alongside the broader effort to make robotics logs easier to inspect outside one vendor or middleware stack.

By 2026 the CLI had advanced to a v0.2.x release line, and the official release notes identify the CLI as rewritten in Rust. That kind of implementation change matters for package managers because it affects build dependencies, binary distribution, and performance expectations.

### Historique d'adoption

MCAP adoption is strongest in robotics and observability workflows around Foxglove and ROS. The official documentation includes guides for getting started, the formal spec, and ecosystem integrations, while Homebrew packages the mcap executable as a convenient desktop and CI tool.

Unlike many robotics formats, MCAP was designed to be serialization-agnostic from the start. That made it attractive for package ecosystems because one CLI can inspect, validate, convert, and filter logs produced by different message schemas.

### Modes d'utilisation

Users install the mcap CLI to inspect metadata, validate files, recover or convert logs, and pipe message data into other tooling. Developers use the spec and language libraries when they need to produce or consume MCAP files directly from robots, simulations, or data pipelines.

The format is especially useful when logs must be archived, replayed, or shared between teams without assuming a single serializer or runtime.

### Pourquoi les passionnés de paquets s'y intéressent

MCAP is package-nerd significant because it turns a robotics logging format into a normal command-line artifact. Having a Homebrew formula for mcap lets developers inspect large log files on laptops without installing an entire robotics distribution.

It also represents a newer class of packages where the file format, spec site, libraries, and CLI are all part of one developer-facing artifact.

### Chronologie

- 2022: Public mcap-cli GitHub releases began.
- 2022: The CLI release stream iterated rapidly through early v0.0.x versions.
- 2026: mcap-cli v0.1.0 and v0.2.0 releases were published, with v0.1.0 described as a Rust rewrite.
- 2026: Homebrew packages the mcap command for local log inspection and conversion workflows.

### Related projects

- Related projects include Foxglove, ROS bags, rosbag2, Protobuf, FlatBuffers, JSON Schema, and robotics telemetry tools that need durable log containers.

### Sources

- <https://github.com/foxglove/mcap>
- <https://github.com/foxglove/mcap/releases>
- <https://mcap.dev/>
- <https://mcap.dev/guides/getting-started>
- <https://mcap.dev/spec>
- source_facts.package-manager


## Notes de sécurité

infrastructure mutation or orchestration signal.

- **Risque Geiger:** orange / moyen
- infrastructure mutation or orchestration signal


## Combined YAML source

View the package source record on GitHub. [combined/mcap.yml](https://github.com/mxcl/pkgdb/blob/main/combined/mcap.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph