Skip to main content
Glama
Sign In
nikitatsym

litellm-mcp

by nikitatsym
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to litellm-mcp

No user-submitted related servers found.

    Related Servers

    • litellm-mcp

      weeebdev
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.
      43 npm
      MIT

    • Ops-Center

      Unicorn-Commander
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables agents to administer a self-hosted AI control plane for users, organizations, subscriptions, API keys, model providers, and service health, with local-first model routing and cloud failover.
      Apache 2.0

    • litellm-admin-mcp

      junwayne66
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes LiteLLM Proxy admin APIs as MCP tools for managing internal users, virtual keys, and spend logs via streamable-http, enabling agents to administer LiteLLM without custom HTTP glue.
      1
      -

    • Woow LiteLLM MCP Server

      WOOWTECH
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server suite for administering LiteLLM gateways, exposing tools to manage models, keys, teams, users, and spending, along with an admin GUI and an encrypted reverse proxy for secure access.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools are separated into clear action categories (read/write/delete/execute/admin/version), which largely avoids confusion. However, litellm_delete and litellm_execute both involve cache deletion, and litellm_admin overlaps with litellm_write for user updates, creating minor boundary ambiguity.

    Naming Consistency4/5

    All tools share the consistent 'litellm_' prefix plus a descriptive word, forming a predictable pattern. The pattern is slightly broken by 'litellm_admin' and 'litellm_version', which use nouns rather than verbs, but this is a minor deviation.

    Tool Count5/5

    Six tools is a well-scoped count for a proxy management server. Each tool represents a broad but coherent category of operations, making the surface area manageable for an agent without being too thin or bloated.

    Completeness5/5

    The tool set covers version/health, read-only queries, create/update, delete, reversible actions, and global admin operations. This provides comprehensive lifecycle coverage for LiteLLM resources with no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources