No user-submitted related servers found.
Scored across 33 tools
Most tools map cleanly to a distinct resource+action in the content pipeline (seeds, sources, drafts, themes, learned preferences). The riskiest pairs are get_draft vs get_draft_kit and mark_draft_ready vs approve_draft, but the descriptions clarify that one is read-only input assembly and the other is a gated state transition. get_cadence_status vs get_calendar has mild overlap but is distinguishable (reminders vs item states).
Nearly all tools follow verb_noun snake_case (capture_seed, list_sources, mark_draft_ready, request_revision, render_outputs). The only deviation is the setup_* prefix used as a noun-first family for write operations, while other writes use action verbs (apply_theme, attach_source) — readable, but two conventions coexist. get_setup also breaks the verb_object shape slightly.
33 tools is heavy for a content engine and exceeds the comfortable range, though the breadth reflects real pipeline stages rather than filler. Some surface could be consolidated (get_seed/list_seeds/search_seeds, kill/revive pairs, seven separate setup_* setters vs one config patcher). Defensible but on the bloated side.
The lifecycle is unusually complete: onboarding config, themes, seeding, research briefs, sourcing, draft versioning, fact-check gating, ready/approve/revision, rendering, sending, and a calendar view. Remaining gaps are minor: no detach/remove for attached sources, no edit/update of a seed body or title (only kill/revive), and no revert of an approved draft.