Research: CLI interface for standalone usage

[jongalloway]

Description

pptx-mcp was designed exclusively as an MCP server for AI assistants, but Phase 4 has produced several tools with strong standalone value — particularly the optimization tools (file size analysis, unused layout removal, media deduplication, image compression). These are useful as one-off operations or in scripted workflows outside of an LLM coding agent scenario.

Research Questions

1. CLI interface design: What would a CLI look like? Options include:

   • \dotnet run\ with command-line arguments (e.g., \pptx-mcp optimize --file presentation.pptx --dpi 150)
   • A separate \pptx-cli\ project that references PresentationService directly
   • A \dotnet tool\ global/local tool package

2. Dual-mode architecture: Can the same binary serve as both MCP server (stdio) and CLI tool (args)? Pattern: if args are present, run CLI mode; if no args, run MCP stdio mode.

3. Candidate commands for CLI exposure:

   • \pptx optimize \ — run all optimizations (compress images, deduplicate media, remove unused layouts)
   • \pptx analyze \ — file size analysis + media analysis report
   • \pptx compress-images --dpi 150 --quality 85\ — image optimization only
   • \pptx deduplicate \ — media deduplication only
   • \pptx cleanup \ — remove unused layouts + masters

4. Distribution: \dotnet tool install\ via NuGet? Single-file publish? Both?

5. Impact on MCP server: Would adding CLI mode affect the MCP server's behavior, startup, or dependencies?

Acceptance Criteria

• Research viable CLI patterns for .NET MCP servers
• Propose CLI command structure
• Evaluate dual-mode (MCP + CLI) vs separate project tradeoffs
• Prototype preferred approach
• Document decision

Notes

• This is a research/spike issue — output is a decision document, not necessarily a shipped feature
• Current PresentationService methods are already well-factored for reuse (thin MCP tools, business logic in service)
• Magick.NET dependency (added in P4-6: Compress/optimize images #85) increases binary size — relevant for distribution decisions

[github-actions]

🔄 Ralph — Auto-Triage

Assigned to: McCauley (Lead)
Reason: No domain match — routed to Lead

Ralph auto-triaged this issue via the squad heartbeat. To reassign, swap the squad:* label.

[github-actions]

🔄 Ralph — Auto-Triage

Assigned to: McCauley (Lead)
Reason: No domain match — routed to Lead

Ralph auto-triaged this issue via the squad heartbeat. To reassign, swap the squad:* label.

[github-actions]

🔄 Ralph — Auto-Triage

Assigned to: McCauley (Lead)
Reason: No domain match — routed to Lead

Ralph auto-triaged this issue via the squad heartbeat. To reassign, swap the squad:* label.

[github-actions]

🏗️ Squad Triage — McCauley (Lead)

Issue: #94 — Research: CLI interface for standalone usage
Assigned to: Cheritto (Backend Dev)
Reason: Issue relates to backend/API work

@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

Team roster:

• McCauley (Lead) → label: squad:mccauley
• Cheritto (Backend Dev) → label: squad:cheritto
• Shiherlis (Tester) → label: squad:shiherlis
• Nate (Consulting Dev) → label: squad:nate
• Ralph (Work Monitor) → label: squad:ralph
• @copilot (Coding Agent) → label: squad:@copilot
• @copilot (Coding Agent) → label: squad:copilot

To reassign, remove the current squad:* label and add the correct one.

[jongalloway]

Decomposition: CLI Implementation (2026-03-24)

Nate's research verdict: GO with dual-mode architecture.

This research issue has been decomposed into 7 implementation sub-issues per the approved design:

Foundation (Blocker):

• CLI: Dual-mode entry point (MCP + CLI) #98: Dual-mode entry point (Program.cs refactor)

Command Groups (Parallel after #98):

• CLI: analyze command group #99: analyze command (file-size, talking-points)
• CLI: optimize command (all-in-one workflow) #100: optimize command (killer workflow: images + dedup + layouts + report)
• CLI: inspect command group #101: inspect command (slides, content, xml, layouts)
• CLI: export command #102: export command (markdown)
• CLI: edit command group (mutations) #103: edit command group (mutations: slide data, batch, tables, images, notes, chart)
• CLI: media/slides command groups #104: media/slides command groups (list, dedup, delete, reorder)

Distribution (Parallel with #99-#104):

• CLI: NuGet global tool packaging #105: NuGet global tool packaging

See decision document: [.squad/decisions/inbox/mccauley-cli-decomposition.md]

Execution Plan:

• Critical path: 22-32 hours, 3 weeks part-time- CLI: analyze command group #99-CLI: media/slides command groups #104 can run in parallel after CLI: Dual-mode entry point (MCP + CLI) #98- CLI: NuGet global tool packaging #105 can start in parallel; final NuGet publish waits on all commands

All issues reference parent issue #94 for context.