crack-mcp
Related Servers
Alternatives to crack-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables reading work outlines, contexts, and chapters, and saving chapters with version protection for an AI novel writing tool.1MIT
- AlicenseAqualityDmaintenanceEnables AI clients to interact with the Fanqie free novel author backend, including listing works, fetching chapter statuses, retrieving statistics, and publishing or drafting chapters.71MIT
- AlicenseAqualityCmaintenanceEnables AI tools to collaboratively write novels by managing chapters, characters, and story state through commands like validate, context, draft, review, and approve.8MIT
- AlicenseAqualityDmaintenanceEnables AI agents to generate SEO-optimized CSDN blog drafts, refine them against a writing style guide, run SEO self-checks, and optionally publish them to CSDN's draft box via browser automation with rate limiting and a human review gate. Also supports session-based login management, local draft library operations, and reading article statistics through CSDN's public API.141MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to create and manage long-form story projects with isolated databases, persistent drafts, canonical continuity checks, controlled updates, and local semantic retrieval through MCP tools, resources, and prompts.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants such as Claude and Cursor to manage a Fanqie Novel author account directly — listing books, publishing or scheduling chapters, tracking per-chapter read and completion stats, checking review notices and violations, and pulling hot-word inspiration. It works over plain HTTP with cookie and CSRF-token authentication, requiring no browser automation.201MIT
TDQS
Scored across 7 tools
The list/get pairings (list_my_stories vs list_story_drafts, get_story vs get_story_draft) are clearly separated by resource (published vs draft), so selection should be reliable. The only real overlap is save_story_draft, which doubles as both create (no storyId) and update (with storyId), but the description spells out that behavior explicitly.
All names are snake_case with a verb-first pattern (list_*, get_*, save_*), which is easy to scan and predictable. Minor deviation: login is a bare verb with no noun, and save_story_draft uses 'save' where other tools would suggest create/update.
Seven tools is well within a healthy range and each one earns its place: two listing tools, two read tools, one write tool, plus limits and auth. Nothing looks redundant or padded for a story draft-editing workflow.
The core loop (list stories, inspect published/draft content, save draft with validation via get_limits, recover auth via login) is fully covered for the stated purpose. Gaps are deliberate or minor: publishing and reflecting edits are explicitly done on the site, but there is no tool to delete a story or draft and no search/filter over stories.