Skip to main content
Glama
troylar

Open WebUI MCP Server

by troylar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Open WebUI MCP Server

No user-submitted related servers found.

    Related Servers

    • librechat-mcp

      Ricky-Hao
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables administration of LibreChat through MCP, providing tools to manage Skills, Agents, scheduled tasks, Prompt library, and visibility/permissions. It also offers a generic API request tool for interacting with upstream endpoints.
      MIT

    • ADMINV2MCP

      hensem
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes AdminV2 backend API operations as discoverable, callable tools for AI agents, enabling natural language or structured API interactions.
      -
    • Okta MCP Server by okta

      Okta MCP Serverofficial

      okta
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to manage Okta organizations through natural language, providing full CRUD operations for users, groups, applications, policies, and system logs via Okta's Admin Management APIs.
      1,042 PyPI
      67
      Apache 2.0

    • Okta MCP Server

      priyamenokey
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to manage Okta organizations through natural language, supporting user, group, application, and policy operations via Okta's Admin APIs.
      Apache 2.0
    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

    B3/5.0

    Scored across 82 tools

    Disambiguation3/5

    The tools cover distinct resources like chats, files, models, and users, but there is significant overlap in CRUD operations across different resource types, which could cause confusion. For example, 'delete_chat', 'delete_file', 'delete_folder', etc., all follow the same pattern but target different entities, potentially leading to misselection if the agent isn't clear on the resource context.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_channel', 'get_channel', 'update_channel', and 'delete_channel'. This predictability makes it easy for agents to understand and navigate the toolset without confusion from mixed naming conventions.

    Tool Count2/5

    With 82 tools, the count is excessive for the Open WebUI domain, making the surface overwhelming and difficult to manage. This many tools suggests poor scoping, as many operations could be consolidated or generalized, leading to potential inefficiency and confusion for agents.

    Completeness5/5

    The toolset provides comprehensive CRUD and lifecycle coverage for all key resources in Open WebUI, including chats, files, models, users, and knowledge bases. There are no obvious gaps, with tools for creation, retrieval, updating, deletion, listing, and specialized actions like sharing or querying, ensuring agents can handle full workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources