Nothing here yet.
Mar 28 · 1 min read · Part 9 of 9 The last piece I cared about was making this useful for learning, not just publishing. That’s where these came in: study_topic_on_substack extract_coding_lessons I wanted Substack to become more than a place to publish. I wanted it to b...
Join discussionMar 28 · 1 min read · Part 6 of 9 The project got a lot more interesting when it stopped being just a publishing tool. That’s where the research layer came in: research_substack research_substack_post research_substack_publication Now the MCP can help discover writers, ...
Join discussionMar 27 · 1 min read · Part 5 of 9 I didn’t want this to be a write-only Substack MCP. If I’m using a tool to publish, I also want it to help me understand what’s happening inside the publication. So I added: get_post_analytics get_sections get_subscriber_count That made...
MAamer commentedMar 27 · 1 min read · Part 4 of 9 The fastest way to tell whether a tool is real or just demo bait is to try the unglamorous parts. That’s why this batch focused on: upload_image duplicate_post delete_draft These are not flashy features. They’re the things that decide w...
Join discussionMar 27 · 1 min read · Part 3 of 9 A lot of MCP demos stop at “draft created successfully” and then quietly hand the real work back to the dashboard. That always felt fake to me. If the promise is “operate this product from an AI client,” then the workflow has to continue ...
Join discussion