I found it much better to write a Skill: Feedback: Using Sprite CLI in an agent
The sprite CLI install process could install skills to well-known paths (eg $HONME/.claude/skills) and have a sprite install-skill subcommand to run in future. This would be just as easy from an end-user perspective, I think! Possibly easier, since you’d only need to grant permission to use sprite, rather than every MCP tool individually.