litellm - 💡(How to fix) Fix [Feature]: Full MCP spec support via the gateway [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#22855Fetched 2026-04-08 00:39:35
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×2cross-referenced ×1
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

The Feature

MCP Specs in LiteLLM should be up to date with https://modelcontextprotocol.io/specification/2025-11-25

Motivation, pitch

Standardization

What part of LiteLLM is this about?

Proxy

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

Twitter / LinkedIn details

No response

extent analysis

Fix Plan

To keep MCP Specs in LiteLLM up to date, implement a periodic sync mechanism.

Steps

  • Update dependencies: Ensure the modelcontextprotocol library is up to date.
  • Create a sync function:
import requests

def sync_mcp_specs():
    url = "https://modelcontextprotocol.io/specification/2025-11-25"
    response = requests.get(url)
    if response.status_code == 200:
        # Update LiteLLM's MCP Specs with the response content
        mcp_specs = response.json()
        # Save mcp_specs to LiteLLM's database or config
        save_mcp_specs(mcp_specs)
    else:
        print("Failed to sync MCP Specs")
  • Schedule the sync function to run periodically (e.g., daily) using a scheduler like schedule or apscheduler.

Verification

Verify the fix by checking the MCP Specs in LiteLLM after the sync function has run. The specs should match the latest version from the modelcontextprotocol website.

Extra Tips

Use a reliable scheduler and implement error handling to ensure the sync function runs consistently and recovers from failures.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Feature]: Full MCP spec support via the gateway [1 participants]