Skip to main content
Glama
marccyberleda

openwebui-mcp-server

by marccyberleda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to openwebui-mcp-server

No user-submitted related servers found.

    Related Servers

    • OpenClaw MCP Server

      hannahito
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude.ai and Claude Desktop to securely connect to self-hosted OpenClaw AI assistants via OAuth 2.1, sending chat messages, checking gateway health, and queuing, polling, or cancelling long-running tasks. Supports orchestrating multiple OpenClaw gateway instances (such as prod, staging, and dev) from a single authenticated bridge.
      96 npm
      MIT

    • obsidian-mcp

      martinblq
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to a local Obsidian vault, enabling listing, reading, searching, and optionally editing notes via natural language, with all operations running locally.
      3,805 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

    A4.1/5.0

    Scored across 26 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action. Even similar operations like removing a file from knowledge vs deleting the file are clearly differentiated in descriptions. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow the consistent pattern `openwebui_<verb>_<noun>`. Verbs and nouns are used systematically, with list tools using plural nouns and singular object tools using singular nouns, maintaining a clear and predictable convention.

    Tool Count4/5

    At 26 tools, the count is on the higher end, but the server covers seven distinct resource areas (chats, knowledge, files, functions, prompts, models, status). Each tool has a clear purpose, though some consolidation could be possible. Overall it's slightly over the ideal range but justified by scope.

    Completeness3/5

    Most core workflows are covered: chats have list/search/get/delete, files have full lifecycle, functions have full CRUD, and knowledge has create/update/add/remove. However, missing knowledge base deletion and prompt detail retrieval are notable gaps, and model operations are limited to listing only.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources