F
licenseNot graded
qualityD
maintenanceConnects Claude to OpenNMS, allowing plain language interaction with alarms, nodes, events, asset records, categories, and service collection.
1
-
openwebui-mcp-server
Related Servers
Alternatives to openwebui-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceConnects Claude to a local Obsidian vault, enabling listing, reading, searching, and optionally editing notes via natural language, with all operations running locally.2,778 npmMIT
- AlicenseBqualityDmaintenanceConnects Claude to a Wiki.js instance, enabling page search, retrieval, listing, and creation.45 npmMIT
- AlicenseAqualityCmaintenanceConnects Claude Desktop to an Obsidian vault, enabling reading, searching, capturing ideas, and managing notes through natural language.218 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude Desktop to your Obsidian vault, enabling reading, writing, searching, and organizing notes locally.1MIT
- AlicenseBqualityCmaintenanceConnects Claude to WordPress sites through the REST API, enabling AI-assisted content creation, publishing, media management, user administration, and site maintenance tasks through natural language.4721 npm22MIT
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