Tempo v2.10.4 released on 13-04-2026
Tempo v2.10.4 is out now. Operators who need to accept or serve MCP (Model Configuration Protocol) configuration flows can enable an MCP server with a new flag.
See the pull request on GitHub for the authoritative change list and the exact flag name and examples: grafana/tempo#6903.
What’s in this release
- Added a flag to enable the MCP server so Tempo can accept and serve MCP configuration flows (PR #6903, contributed by @tiffanyfay).
- Documentation and usage notes on where the flag appears: startup/CLI options, Tempo configuration files, service/container arguments and Helm/Kubernetes manifests.
- Release metadata and links: timestamp 2026-04-13 11:20:01 and the PR for implementation details and examples (grafana/tempo#6903).
Upgrade notes
- No breaking changes or deprecations are listed for v2.10.4; operators should test enabling the MCP server in a staging environment and validate networking, ports and ACLs for the MCP endpoint (consult the PR/docs for the exact flag name).
- Rollback: disable the MCP server flag if issues appear after enabling; monitor logs and metrics while testing to confirm behaviour.
Let us know how enabling the MCP server worked in your environment and share any issues or suggestions from your testing.
