跳至主要內容

2 篇文章 含有標籤「mcp」

檢視所有標籤

July stability update: hardening MCP auth and cutting pass-through memory

Ishaan Jaffer
CTO, LiteLLM
Tin Lo
Tin Lo
MCP Eng, LiteLLM
Mateo Wang
AI Engineer, LiteLLM
Yassin Kortam
Senior SWE @ LiteLLM

Over the last two weeks we addressed two major product quality issues:

  1. The MCP Gateway did not have a single class for credential resolution.
  2. Pass-through APIs had high memory consumption.

Across the same window we shipped 134 bug fixes in total. This post covers the two big changes first, then the rest of the AI Eng and reliability work, the full breakdown, and what we are doing next.

5 ways to cut Claude Code costs with LiteLLM

Krrish Dholakia
CEO, LiteLLM

5 ways to save Claude Code cost with LiteLLM

Claude Code is one of the heaviest consumers of input tokens in a modern engineering org. Long tool loops, large file reads, and MCP catalogs with hundreds of tools push every request toward the top of the context window, and the bill scales with it.

If Claude Code already points at a LiteLLM proxy (via ANTHROPIC_BASE_URL), there are five levers the platform admin can pull to bring that cost down. None of them require a client-side change.