Shuck File
Give agents a single MCP tool to open arbitrary project files and receive Markdown-focused extracts instead of dumping whole binaries into context.
Overview
shuck-file is an MCP server for the Build phase that turns arbitrary local files into Markdown extracts so agents read only the relevant content.
What is this MCP server?
- Any supported file in → Markdown out for token-efficient agent reads
- Emphasizes reading only what matters rather than full-file passthrough
- stdio PyPI package shuck-file v2.0.4 for MCP hosts
- Complements format-specific converters when you need unified ingestion
- MCP read path for local repos, not a cloud document DAM
- Published as shuck-file PyPI package at version 2.0.4
- Single stdio MCP package per server.json schema
Community signal: 6 GitHub stars.
What problem does it solve?
Agents either skip important non-code files or blow the context budget ingesting entire binaries and exports.
Who is it for?
Solo builders running Claude Code or Cursor who want one ingestion primitive across many file types in a monorepo.
Skip if: Workflows that only need DOCX/PDF conversion with Word export, or teams that forbid local file access from agents.
What do I get? / Deliverables
Once registered, the agent can request Markdown views of project files with a consistent MCP read tool.
- Markdown representations of requested local files
- Token-sized extracts instead of raw binary context
Recommended MCP Servers
Journey fit
File-to-Markdown reading is Build work: agents need grounded snippets from code, config, and docs while implementing features. Agent-tooling is the shelf because the value is MCP plumbing that shapes what the model sees, not publishing finished docs.
How it compares
Unified file-read MCP server, not a dedicated PDF-to-DOCX converter skill.
Common Questions / FAQ
Who is Shuck File for?
Builders who wire MCP into their agent and need dependable Markdown summaries from assorted repo and workspace files.
When should I use Shuck File?
Use it during Build and Operate when the agent must inspect attachments, exports, or non-source artifacts without manual copy-paste.
How do I add Shuck File to my agent?
Install Shuck File from PyPI, configure an MCP stdio server entry for identifier Shuck File, and grant the host read access to allowed paths.