Shuck Convert
Let your coding agent convert PRDs, contracts, and exports between DOCX, PDF, and Markdown without leaving the session.
Overview
shuck-convert is an MCP server for the Build phase that converts DOCX and PDF to Markdown and Markdown back to DOCX for agent-driven documentation workflows.
What is this MCP server?
- Bidirectional DOCX ↔ Markdown conversion for agent-editable specs
- PDF → Markdown for scraping requirements from locked PDF exports
- Markdown → DOCX for stakeholder or legal review rounds
- stdio PyPI package `shuck-convert` v1.0.0 for Claude Code–style MCP hosts
- MCP integration for document pipelines, not a standalone desktop converter app
- Server schema version 1.0.0 with one PyPI package and stdio transport
- Supports DOCX/PDF ↔ Markdown conversion paths per catalog description
Community signal: 1 GitHub stars.
What problem does it solve?
Builders waste context window and manual effort retyping PDFs and Word docs instead of feeding agents structured Markdown.
Who is it for?
Indie builders who ingest customer PDFs or Word specs and want one MCP tool for Markdown-centric repos.
Skip if: Teams that need pixel-perfect PDF layout, batch OCR at scale, or non-agent GUI conversion only.
What do I get? / Deliverables
After you register the server, agents can pull readable Markdown from office files and push polished DOCX exports without a separate conversion step.
- Markdown text derived from DOCX or PDF inputs
- DOCX files generated from agent-edited Markdown
Recommended MCP Servers
Journey fit
Format conversion sits in Build because solo builders turn messy office files into repo-friendly Markdown while writing specs and documentation. Docs is the canonical shelf: deliverables are Markdown drafts, Word handoffs, and readable extracts from PDFs—not live app code.
How it compares
MCP document converter, not a general-purpose skills.sh writing skill.
Common Questions / FAQ
Who is Shuck Convert for?
Solo builders and agent users who routinely move content between DOCX, PDF, and Markdown during product and docs work.
When should I use Shuck Convert?
Use it in Build when onboarding legacy documents into your repo or exporting agent-written Markdown for reviewers who need Word.
How do I add Shuck Convert to my agent?
Install the PyPI package Shuck Convert, add an MCP server block with stdio transport pointing at that package, and restart Claude Code or your compatible host.