OpenFic MCP
Related Servers
Alternatives to OpenFic MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server for managing Foundry VTT journal content (entries, categories, pages) and listing actors, enabling AI-assisted world-building via natural language commands.11-
- AlicenseAqualityAmaintenanceA read-only MCP server that connects to Calibre-Web ebook libraries via OPDS feeds, enabling AI assistants to search and browse books, shelves, covers, and library statistics.643 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for managing and playing a running SillyTavern instance, enabling AI coding assistants to read/write character cards, worldbooks, and chats, and to interact as a player via the full generation pipeline.19-
- AlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes Scrivener projects to AI clients, enabling project creation, binder navigation, document read/write, and metadata updates without opening Scrivener.104 npm1AGPL 3.0
- AlicenseAqualityAmaintenanceA read-only MCP server so AI agents can query the corpus or the live site.21716MIT
- AlicenseAqualityAmaintenanceAn MCP server that lets local AI agents read and manage OpenProject project data through structured, guarded tools, with write operations requiring explicit confirmation.14337 PyPI25MIT
TDQS
Scored across 22 tools
Each tool targets a distinct resource and action: list/get/search are consistently separated, and worldbook tools are differentiated by purpose (by ID vs project-configured). No two tools appear to do the same thing.
All tools follow a clear verb_noun pattern (list_, get_, search_, read_, openfic_health being the only exception, but that is a distinct health check). The naming is consistent and predictable.
22 tools is slightly above the typical range, but each tool earns its place given the breadth of entity types (projects, volumes, chapters, summaries, characters, notes, worldbooks). The count is reasonable for the scope.
The read-only surface covers all major entities with list/get/search variants, leaving no obvious dead ends for reading. Write operations (create/update/delete) are absent, but the server appears intentionally read-only for context provision, so only minor gaps like search_projects exist.