docs - expose MCPs on public internet

[ishaan-jaff]

docs - expose MCPs on public internet

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Building	Preview, Comment	Feb 7, 2026 2:24am

[greptile-apps]

Greptile Overview

Greptile Summary

• Adds a new MCP documentation page describing IP-based filtering of MCP servers via available_on_public_internet and mcp_internal_ip_ranges, including UI walkthrough + API/config examples.
• Wires the new doc into the Docusaurus sidebar under the existing /mcp documentation section.
• The change is documentation-only (no runtime code changes), but the new page includes some potentially fragile/incorrect examples that could cause doc rendering or copy/paste issues if not corrected.

Confidence Score: 3/5

• This PR is low risk to merge (docs-only), but a couple of documentation issues could cause user confusion or rendering quirks.
• Docs-only changes reduce merge risk, but the new page appears to include (1) angle-bracket placeholders that may be parsed as HTML in MDX and (2) unverified REST API endpoint paths for MCP server CRUD. If either is wrong, users will hit immediate copy/paste failures.
• docs/my-website/docs/mcp_public_internet.md

Important Files Changed

Filename	Overview
docs/my-website/docs/mcp_public_internet.md	Adds a new MCP doc page describing available_on_public_internet filtering based on caller IP; includes walkthrough screenshots and example API/config snippets. Potential doc build/maintenance issues due to heavy use of external images and unescaped angle-bracket placeholders in inline code blocks.
docs/my-website/sidebars.js	Adds mcp_public_internet to the /mcp docs sidebar category; change is localized and syntactically consistent with existing sidebar structure.

Sequence Diagram

sequenceDiagram
  participant Ext as External MCP client
  participant Int as Internal MCP client
  participant Proxy as LiteLLM MCP endpoints
  participant IP as IP classifier (mcp_internal_ip_ranges)
  participant Store as MCP server store

  Ext->>Proxy: GET /mcp (registry / tools/list)
  Proxy->>IP: classify(client_ip)
  IP-->>Proxy: external
  Proxy->>Store: load MCP servers
  Store-->>Proxy: servers (public+private)
  Proxy-->>Ext: only available_on_public_internet=true

  Int->>Proxy: GET /mcp (registry / tools/list)
  Proxy->>IP: classify(client_ip)
  IP-->>Proxy: internal
  Proxy->>Store: load MCP servers
  Store-->>Proxy: servers (public+private)
  Proxy-->>Int: all servers

  Ext->>Proxy: POST /mcp (tools/call)
  Proxy->>IP: classify(client_ip)
  IP-->>Proxy: external
  Proxy-->>Ext: allow only if target server is public

Loading

[greptile-apps]

_{2 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

HTML placeholder may break

The snippet uses <your-litellm-url>/mcp inside a fenced code block. In MD/MDX, angle-bracket placeholders can be interpreted as an (invalid) HTML tag and may get stripped or rendered oddly, so readers may not see the literal placeholder. Prefer a plain-text placeholder without <...> (e.g. YOUR_LITELLM_URL/mcp) or escape the brackets (e.g. <your-litellm-url>/mcp).

[greptile-apps]

Docs example endpoints inconsistent

The API examples use /v1/mcp/server for both create and update. If the actual REST endpoints are /v1/mcp/servers (plural) or a different path (common pattern elsewhere in the docs), these snippets will mislead users and cause copy/paste failures. Please confirm the exact MCP server CRUD endpoints used by the proxy and align the docs accordingly (including whether updates are PUT /v1/mcp/server/{id} vs body server_id).

[greptile-apps]

External screenshots are brittle

This page embeds many external colony-recorder.s3.amazonaws.com images. These links are likely to expire or become inaccessible, which will break the docs page rendering/UX. Consider moving key screenshots into the repo under docs/my-website/static/img/ (or switching to fewer, representative images) so the docs remain stable.