Comment by jphorism
3 days ago
Awesome stuff. Seems to me like one great use case of an MCP for Ableton would be to develop muscle / workflow memory for music production workflows. Adjacently, I've started using Perplexity a bunch for this sort of thing because it indexes YouTube tutorial transcripts. Any thoughts on how to design MCPs for learning Ableton better?
One thing I don’t cover in the blog post is ensuring your MCP tool calls are well documented. (If it’s an existing MCP you can do this with a README or instructions file.) I saw a jump in efficiency when I manually edited the docstrings with examples of when each tool would be used, how to call it, and better argument descriptions.
That's cool! Have you thought about some docstring augmentation loop -- either by having the agent log the tool uses or by auto querying (e.g. perplexity API) for example use cases in the wild?
Would be forever grateful for a repo to learn from, even if its rough.
https://github.com/jhurliman/ableton-mcp/pull/1