Release Notes — 2.62

Covers the 2.62 release series. Most recent patch: 2.62.1.

Unless a subsection notes otherwise, changes apply to both Monad SaaS and self-hosted.

New features & improvements

• Hosted MCP service & Connected Apps — Monad now runs a hosted Model Context Protocol (MCP) service and adds a Connected Applications area with an OAuth org picker, so you can connect Monad to MCP-compatible AI clients and manage those connections in one place.
  • Access: opt-in — connect and manage apps under Settings → Connected Applications.
• Alert Rules management — Alert rules can now be enabled or disabled individually from a per-row toggle, are grouped by alert category, and show a clear indicator for system-managed rules, making it easier to see and control exactly which rules are active.
  • Where: Alerts → Alert Rules.
• Custom pipeline edge names — You can give pipeline edges your own labels in the V2 pipeline builder, so branching flows read clearly at a glance.
  • Access: opt-in — edit an edge's label in the pipeline builder.
• Firehose input: templating & connection pooling — The Firehose input adds a templating option plus connection-pool controls, giving you more flexible routing and better throughput on high-volume streams. Docs →
  • Access: opt-in — configure templating and pool options in the Firehose input settings.

New connectors

None this series.

Fixes

• Org selection survives multiple sign-in replicas — Signing in no longer loses your selected organization when the login service runs more than one replica.
• Azure Blob Storage input accepts arbitrary time formats — The Azure Blob Storage input now parses non-standard timestamp formats instead of failing on them.
• Azure Event Hubs input state race fixed — A race condition when saving Event Hubs consumer state is resolved, preventing occasional state corruption.

Breaking changes

Self-hosted only

• Outbound SSRF protection is now on by default — Monad's HTTP client now blocks outbound requests to private / internal network addresses (loopback, RFC1918 IP ranges, and internal hostnames) by default. Previously there was no such restriction, so a self-hosted deployment that routes a pipeline to an internal or private host — a private output, input, or enrichment endpoint on your own network — will find those connections blocked after upgrading. (Monad's own in-cluster calls, such as SSO to an in-cluster identity provider, are exempted automatically and are unaffected.)
  • Action: before upgrading to 2.62.x, list the internal hosts you need to reach in the Helm value MONAD_ENV_ALL__MONAD_INTERNAL_HOSTS (forwarded into the pipeline pods) — and MONAD_INTERNAL_HOSTS on the api — as comma-separated hostnames, IPs, or CIDRs. Use * to allow all and restore the previous behavior.

Need help?

See the Monad docs for setup guides and reference, or reach out to Monad Customer Support at support@monad.com or via your dedicated Slack customer channel.