Off Shoring MCP
Related Servers
Alternatives to Off Shoring MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceContinuity by Ouroboros Apps (https://ouroborosapps.com). Story continuity for fiction writers: a series bible and novel memory that keeps characters, places, timelines, and plot facts consistent across chats. Connect by pasting https://continuitywriter.com/mcp into Claude, Cursor, Grok, or ChatGPT (OAuth). Docs: https://ouroborosapps.com/docs/continuity11MIT
- AlicenseAqualityCmaintenanceEnables persistent, model-driven text adventures with transactional saves, character knowledge boundaries, cited canon retrieval, dice outcomes, and forkable historical timelines via MCP tools and local SQLite storage.17MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server for end-to-end SFW game authoring and project-state management, covering scaffolding, canon and cast records, dialogue and scene systems, story and level design, accessibility checks, asset provenance routing, playtesting, and release handoff. It enforces lane and canon gates before canonical writes and produces deterministic, reproducible game data with provenance.-
- AlicenseNot gradedqualityBmaintenanceEnables long-form web novel writing workflows by ingesting chapters into a state database, running deterministic consistency checks, querying entity histories, replaying extraction results, and retrieving conflict reports via MCP tools.MIT
- AlicenseAqualityDmaintenanceA local MCP server for maintaining internal consistency in fiction writing, with constraint-based fact checking, branching, and author-oracle conflict resolution.27MIT
- AlicenseBqualityDmaintenanceEnables writers and AI agents to preserve continuity in long-form fiction by maintaining a narrative knowledge graph and exposing MCP tools for querying outlines, entities, references, and consistency diagnostics.14MIT
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: create/update/delete/list/export story, append turn, read turns, and branch operations are well separated. The only mild overlaps are select_branch vs branch_story (both branch-related) and read_turns vs get_story_context (both read turn data), but their descriptions make the boundaries clear.
All tool names follow a consistent snake_case verb_noun pattern: select_branch, export_story, delete_story, list_stories, create_story, get_story_context, read_turns, update_story, append_turn, branch_story. No mixed conventions or vague standalone verbs.
Ten tools is well-scoped for a story management server with branching and turn history. Each tool covers a distinct operation, and there is no obvious filler or redundant tool.
Core lifecycle is covered: create/list/get/update/delete/export stories, append/read turns, select/branch stories. Minor gaps exist around explicit branch listing or branch deletion and direct turn deletion, but these may be intentional due to the immutable-turn design; agents can work around them via context and export.