From 82b37a76356e94b81faeb685fefea2a781a1cda5 Mon Sep 17 00:00:00 2001 From: Amolith Date: Wed, 22 Oct 2025 13:03:50 -0600 Subject: [PATCH] docs: fix typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 43015a1db3f99601d1f75fd4b2c77dde0d5218f6..6c6709c901011bf7593f97dca4746f73c7d9178b 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ 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 +few simple CLI invocations. Maybe connecting arbitrary 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.