Phase 4.6 — Public website
kimiship.cc is live as a static Cloudflare Pages site.
Pages cover how the product works, connector setup, security practices,
and current status. Sitemap, security headers, and canonical domain
redirect are all configured.
Phase 4.5 — Remote composer & approval
Authenticated web UI at app.kimiship.cc.
Review drafts in browser, mark them reviewed, and approve for
publishing. Approval state is stored in Postgres and visible to
Claude in the next session via list_draft_sets.
Phase 4 — Content quality & voice
Draft validation against platform rules and brand guidelines.
validate_draft checks character limits, hashtag counts,
empty body, and your stored brand banned-word list. Draft repurposing
via repurpose_draft — adapt an approved draft to a
different platform.
Phase 3 — Remote MCP for Claude.ai
Remote MCP endpoint at mcp.kimiship.cc using
OAuth 2.1 + PKCE (RFC 8707, RFC 9728). Claude.ai can connect
via the Connectors UI. All previous Phase 1–2 tools available
remotely. Data stored in Neon Postgres with owner-scoped
row-level security.
Phase 2 — Brand voice & ideas
Brand profile storage: tone, style, example posts, and a
banned-word list. Content ideas library. Generation context
(get_generation_context) loads brand data into
Claude's session. Draft repurposing and multi-platform drafts
from one idea.
Phase 1 — Draft & voice MVP
First usable MCP tools: create_draft_set,
list_draft_sets, get_draft_set,
update_draft, approve_draft,
archive_draft. Local SQLite storage. Audit log
(action, actor, no body content). Multi-platform draft sets
(LinkedIn, Instagram, TikTok, X).
Phase 5 — Calendar & scheduling
Planned module. Schedule approved drafts with a publish date and time. Calendar view of scheduled content. Not yet available.
Module A — Publishing
Planned module. Post to LinkedIn, Instagram, TikTok, and X directly from KimiShip. Not yet available.
Module B — Media generation
Planned module. Claude-prompted image and video generation via external providers (BYOK model). Not yet available.