A
licenseNot graded
qualityB
maintenanceEnables MCP-capable assistants to read files, work packages, and wiki pages from an openDesk instance using the account's existing permissions.
1
Apache 2.0
xwiki-mcp
by Nraitschew
Related Servers
Alternatives to xwiki-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables read-only retrieval of Jira Cloud issues, JQL search, and project issue listing through MCP tools.331 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables read-only access to GitLab projects, files, directories, and merge requests through MCP tools.-
- AlicenseAqualityBmaintenanceEnables read-only access to LCM2M Caddis VM2M API for equipment, runs, telemetry, alarms, etc., via MCP tools.314 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.4 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables read-only querying of Jira Server/Data Center projects, issues, comments, transitions, and issue types through MCP tools.331 npmMIT
TDQS
A4.3/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct resource/action: full-text search, single page retrieval, space listing, in-space page listing, attachment listing, and wiki listing. Although list_spaces and list_wikis sound similar, their descriptions clearly separate spaces within a wiki from wiki instances on a farm. No two tools appear interchangeable.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern: search_pages, get_page, list_spaces, list_pages_in_space, list_page_attachments, and list_wikis. All use lowercase snake_case and list_ for enumeration operations. Minor singular/plural variation is natural and does not create confusion.
Tool Count5/5
Six tools is well-scoped for a wiki browsing/reading server. Each tool has a clear role in navigation or retrieval, with no redundancy. The count is not excessive for the feature set.
Completeness4/5
The server covers the core read/browse cycle: discover wikis, navigate spaces, search/list pages, fetch page content, and see attachments. The only notable gaps are that attachment contents cannot be fetched and there are no page lifecycle operations, but the exposed surface appears intentionally read-oriented. No critical dead end blocks typical wiki research.
Maintenance
ActivityMaintained
ResponsivenessNo issues