OpenTelemetry Weaver CLI
Weaver validates, resolves and diffs OpenTelemetry semantic conventions, and its MCP mode feeds attribute names to your agent
- 521 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- generate and update-markdown write files into the project
- emit sends example signals to the OTLP receiver you set, and MCP mode reads the registry and accepts telemetry samples
Install
- Works in
Manual install
docker pull otel/weaverPrebuilt binaries for Linux, Windows and macOS are on the releases page; building from source uses cargo build --release.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- generate and update-markdown write files into the project
- emit sends example signals to the OTLP receiver you set, and MCP mode reads the registry and accepts telemetry samples
This is third-party code. Review the repository files before installing.
What it does
Weaver is an OpenTelemetry command-line program for working with semantic convention registries, that is, the definitions of attributes, metrics, spans and events. weaver registry check validates a registry, resolve expands it and diff compares two versions. generate produces code and documentation from templates, for example Go code or Markdown, and update-markdown refreshes marked sections of Markdown files. Two commands handle live telemetry. registry live-check compares an OTLP stream with the registry, and registry emit sends example signals to your OTLP receiver. weaver registry mcp starts an MCP server with eight tools. search covers attributes, metrics, spans, events and entities, get_attribute, get_metric, get_span, get_event and get_entity return details, browse_namespace walks the hierarchy by prefix, and live_check validates telemetry samples. The built-in advisors flag deprecated and experimental items, type mismatches and invalid enum values.
Who it is for. Platform engineers and service authors on OpenTelemetry who treat their telemetry as a public API and write instrumentation together with an agent.
Good fit when
- Metrics were renamed in code while alerts stayed the same, and you want to catch such drift in CI before release
- An agent writes HTTP server instrumentation and has to take exact attribute names from the registry
- Two registry versions have to be compared to see what changed
- The app already sends OTLP and you want to check whether the signals match the schema
- Attribute tables in the documentation should refresh from the registry automatically
Not a fit when
- You need a step-by-step guide to wiring the OpenTelemetry SDK into your language: Weaver works with registries and schemas
- The task is querying data in a metrics or tracing backend: none of the Weaver commands does that
- The machine cannot run binaries or Docker and building Weaver from Rust sources is not an option
Example request
Look up HTTP server attributes in the Weaver registry and check that my spans use themLimitations
- For MCP mode the agent needs the path to the weaver binary, and a custom registry is passed with the --registry argument.
- Step-by-step connection instructions exist only for Claude Code; for other clients use that client's documentation.
- The live_check tool reports problems and leaves the instrumentation code alone.
- Ready installers for Linux, Windows and macOS are on the releases page, and the Docker image is called otel/weaver. Building from source needs Rust and cargo.
How to disable. Remove the server with claude mcp remove weaver. Delete the Docker image with docker rmi otel/weaver and the installed binary by deleting the file.
FAQ
How do I connect Weaver to Claude Code?
Run claude mcp add --transport stdio weaver /path/to/weaver -- registry mcp with the path to your binary. Then ask the agent about HTTP server attributes and it calls the search tool.
Which tools does the Weaver MCP server have?
Eight: search, get_attribute, get_metric, get_span, get_event, get_entity, live_check and browse_namespace. The main one is search, which takes a query, a type, a stability filter and a result limit, 20 by default.
Can I check an application's telemetry against the registry?
Yes. registry live-check accepts an OTLP stream, and the live_check MCP tool validates the samples you pass and returns only findings in findings_only mode.
How do I install Weaver?
Download an installer for Linux, Windows or macOS from the releases page, run docker pull otel/weaver or build the program from source with cargo build --release.
What does weaver registry generate do?
It produces artifacts from the registry using templates: code, for example Go, and Markdown documentation. update-markdown refreshes sections in existing Markdown files.
Discussion
No questions or reviews yet.
Related
CLI toolsA local dashboard for Claude Code, Codex CLI, Gemini CLI, Copilot and OpenCode that shows tokens, cost, latency and errors
MCP Gateway Registry
mcp-gateway-registry
One registry and gateway for MCP servers, agents and skills: shared login, OAuth, audit, OpenTelemetry. Community project for Docker and cloud
A marketplace of OpenTelemetry plugins for Claude Code, Codex, Copilot and other agents that checks and follows releases itself.
OpenTelemetry Agent Skills helps agents instrument applications, configure Collector and check versions against primary sources.
A Git merge driver and MCP server that compares functions and classes and removes false conflicts from parallel agent edits
OpenTelemetry-based CLI tracing for Claude Code, Cursor and Codex sessions, showing what the agent actually did and what it cost
README in short
The README sets out the idea of observability by design: observability signals are treated as a public API held to the same quality bar as code. It then covers installation from prebuilt binaries, Docker and source, the main commands, examples and links to project talks. A setup-weaver action exists for CI.