LiteLLM v1.106.0-dev.1: Docker Image Signing, New Integrations, and MCP Change
LiteLLM v1.106.0-dev.1 introduces cosign-signed Docker images, new Microsoft 365 Graph and gateway providers, a one-command quickstart, and disables stdio MCP servers by default.
What changed?
LiteLLM v1.106.0-dev.1 includes several noteworthy updates: - All Docker images are now signed with cosign. Each release uses the same signing key, providing verifiable image integrity ([source](https://github.com/BerriAI/litellm/releases/tag/v1.106.0-dev.1)). - Microsoft 365 (Graph) server is added to the MCP catalog. - The release disables stdio MCP servers by default, a breaking change for users relying on those integrations. - New gateway and open source classifier providers such as Laya and Bespoke Nimble are now supported. - A one-command quickstart is introduced to start the gateway, Postgres, and admin UI together.
Why does it matter to an everyday developer?
Docker image signing allows developers and organizations to verify that the images they deploy have not been tampered with, enhancing supply chain security. The new integrations—Microsoft 365 (Graph) server in MCP, Laya, and Bespoke Nimble providers—increase the range of services and AI models LiteLLM can manage and orchestrate. The one-command quickstart lowers the barrier to evaluation and deployment, saving setup time. The removal of stdio MCP server defaults requires users with custom setups to revisit and possibly update their configurations.
What can the developer do now?
- Verify the authenticity of Docker images using cosign following the official guidance in the release notes.
- Update MCP server configurations if your workflows depended on stdio servers—they are now disabled by default.
- Try the one-command quickstart script to spin up LiteLLM, Postgres, and its admin UI for faster local development or testing.
