planist-mcp
Related Servers
Alternatives to planist-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to safely read, write, edit, search, and optionally run commands within one or more named project workspaces, while maintaining a work journal and tracking changes.19MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI apps to create, organize, and share notes, pages, and small database-backed apps in a personal workspace through a single remote MCP connector.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely access and manage PlainStaff workspaces for time tracking, project bookings, absences, shift plans, and compliance reporting through MCP, with dry-run write confirmation for safe operations.MIT
- AlicenseAqualityAmaintenanceMCP server for DocsMint, an AI-native knowledge workspace. It gives AI agents scoped access to search, read, create, update and organize documents using hybrid retrieval and GraphRAG.22118Apache 2.0
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for accessing GitBook content, including spaces, pages, and search, through AI assistants.30 npmMIT
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4319MIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation on either pages or variables: list/read/propose for pages, and list/get/update for variables. There is no overlap or ambiguity between them.
All tool names follow the consistent planist_<verb>_<noun> pattern using snake_case. Verbs are clear and specific (list, read, get, propose, update), making the naming predictable and coherent.
With six tools, the server is well-scoped for managing pages and variables. The count is within the ideal 3-15 range and each tool serves a clear purpose without unnecessary bloat.
The server covers read, list, and update operations for both pages and variables, but lacks any creation or deletion capabilities. This is a notable gap in the resource lifecycle, though the propose-edit workflow adds a distinct review step for page modifications.