Skip to main content
Glama
TETRA-2023

open-webui-mcp

by TETRA-2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to open-webui-mcp

No user-submitted related servers found.

    Related Servers

    • openwebui-mcp

      vedmaka
      A
      license
      Not graded
      quality
      C
      maintenance
      Open WebUI MCP server that exposes ask and list_models tools, letting any MCP client query Open WebUI models through the full tool-calling loop (including server-side tools) via stdio, SSE, or streamable HTTP transports.
      5
      MIT

    • litellm-mcp

      nikitatsym
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the LiteLLM proxy, enabling agents to administer resources like keys, teams, users, models, and proxy settings through risk-graded meta-tools.
      6
      MIT

    • openhab

      deswong
      A
      license
      C
      quality
      C
      maintenance
      MCP server for OpenHAB v5+ that exposes the entire REST API as tools for AI models, enabling complete control over items, things, rules, persistence, and semantic model.
      25
      7
      MIT

    • mcp-openai-platform

      cyclomax-x
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server exposing the OpenAI platform REST API as tools for file management, fine-tuning, inference, images, audio, batch processing, and organization usage/costs.
      -

    • 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.
      8 npm
      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

    D1.7/5.0

    Scored across 317 tools

    Disambiguation1/5

    Many tools have overlapping purposes, such as multiple 'Get Models' and 'Process Web' endpoints with indistinguishable descriptions. The vast number of similar tools makes it nearly impossible for an agent to consistently select the correct one.

    Naming Consistency2/5

    While there is a general pattern of verb_noun_api_v1_resource_action, the naming is highly inconsistent: duplicate tool names, missing action suffixes, and extremely long names make it confusing. The pattern breaks down frequently.

    Tool Count1/5

    At 317 tools, the count is far too high for a coherent surface. This suggests a lack of abstraction and many tools that could be combined or parameterized. It overwhelms any agent trying to use this server.

    Completeness3/5

    Despite the excessive count, the tools cover a wide range of Open WebUI functionality, including CRUD for many resources, authentication, file operations, and retrieval. However, there are some gaps (e.g., update missing for some resources) and redundant tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources