collectives-mcp
Related Servers
Alternatives to collectives-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceA MCP server for accessing Nextcloud Collectives, allowing MCP clients to list, read, and edit collectives, their pages, and tags.-
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that exposes Nextcloud files, calendar, notes, and search as tools for Claude.ai, authenticating via Nextcloud OAuth.MIT
- AlicenseNot gradedqualityAmaintenanceA curated MCP server that connects your Nextcloud (files, calendar, notes, deck, contacts) to AI assistants.14AGPL 3.0
- FlicenseBqualityDmaintenanceMCP server integrating Nextcloud services (tasks, calendar, notes, email, files, Deck) for AI assistant interaction.201-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables Claude to list, read, write, create, delete, and search files on a self-hosted Nextcloud instance via WebDAV, with additional Obsidian vault-aware operations for frontmatter, tags, backlinks, and wikilinks.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that lets Claude create calendar events and tasks in Nextcloud via CalDAV.-
TDQS
Scored across 57 tools
Most tools use a clear resource+action pattern, so pages, tags, templates, attachments, and shares are easy to tell apart. A few near-neighbors require careful reading, such as search vs search_in_collective, update_collective vs set_page_mode, and update_template vs update_template_content, but their descriptions disambiguate them effectively.
The snake_case verb_noun convention is strong and consistently used across collectives, pages, tags, templates, attachments, and shares. Minor deviations like search and ping as bare verbs, plus the inconsistent permanent-delete terms (permanently_delete_collective vs purge_page), keep it from a perfect 5.
With 57 tools, this is far beyond a typical agent-facing MCP surface and creates significant selection overhead. Even though the domain is broad, the count sits in the extreme-mismatch range and would benefit from consolidation or splitting into smaller focused servers.
The surface covers nearly all lifecycle operations for collectives, pages, tags, templates, attachments, and shares, including trash, versions, and search. Minor gaps exist, such as no way to list favorited pages or list/purge trashed attachments, but agents can generally work around them.