From 386c7dbb7a0041614c4f6dfdae579b3f1e94b597 Mon Sep 17 00:00:00 2001 From: Amolith Date: Wed, 22 Oct 2025 12:47:32 -0600 Subject: [PATCH] docs: mention why CLI over MCP --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index e5e886cb01b273bb4363657ef9220472d0a8521a..fc3e6d389c022a12315ce33eda8b19bc3e4ff895 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,13 @@ [![Go Report Card](https://goreportcard.com/badge/git.secluded.site/nasin-pali)](https://goreportcard.com/report/git.secluded.site/nasin-pali) **This README is aspirational!** None of the code exists yet, I'm just getting -my ideas down. +my ideas down. I previously wrote a +[planning-mcp-server](https://git.secluded.site/planning-mcp-server) that I'll +keep some ideas from, and the overall workflow is about the same. I'm trying a +CLI over MCP because MCP seems quite protocol-heavy for what _could_ just be a +few simple CLI invocations. Maybe connecting arbitrarty data sources warrants a +whole protocol like MCP, but I don't think something as basic as this does. Just +some thoughtful design and prompting. ---