Lesson 24 of 30, Module 4: Ship It. It publishes to Substack, runs on the web, and anyone can install it.
What you can do after this lesson
When you automate a chain, the last manual step is where the original problem comes back. Before you build the fix, know what it costs and which parts are free. Keep the one irreversible action, sending to your audience, as a human click.
The problem we inherited
The draft is finished in Drive and still goes nowhere. You copy it into Substack by hand, which is exactly where you came in.
Downloads
- Module 4 checkpoint (scribe-checkpoint-m4.zip): working code as the module leaves it, so a broken session costs you nothing
- The course GitHub repo: every checkpoint, the README and the full lesson list
Lesson transcript
The draft is done, and I still copy it by hand
The draft is finished. It sits in my Drive, fixed, with my style rules applied. And then I open Substack, and I copy it in by hand.
Hello, and welcome to lesson 24 of the MCP Masterclass, and welcome to module 4, the last one. In module 3 you made Scribe safe to trust. Today we look at the 1 step that is still manual, and at the promise this module pays. And we start with our map, as always.
The map: 13 lit, 3 dark
13 lit boxes. The guard and the memory are on, beside your 5 tools. And there are 3 dark boxes left. Publish draft, down at the bottom of the tool column. The web address, under the pipe. And the registry, at the very bottom of the map.
What already works
Well, I want to start with where you are, because it is a good place.
Here is my Drafts folder in Drive. The draft is still called draft.md, and it still has the typo from lesson 17 in it, because I put it back for you.
On screen: draft.md in the Drafts folder in Drive. "# My first draft" and "This is a test. Ths line has a typo in it."
And here is memory.json, next to my server. 2 notes in it, from module 3. My openings stay under 12 words, and the launch post goes out on Monday.
On screen: memory.json, 2 entries, each with a date and a note.
So Claude can read that draft, fix it, and it asks me before it writes. It knows my rules, in every app, in every chat. All of that is yours now, and it works.
The last manual step
And then the draft is done. And it goes nowhere.
I open Substack in a browser. I make a new post. I copy the draft out of Drive, and I paste it in, and I fix the headings by hand. That is the last manual step.
Do you remember lesson 1? That is exactly where we came in. You were copying a document into a chat, and pasting the edits back. We moved the copying to the end of the line, and it is still there.
So that is the problem module 4 inherits. The draft is finished, and you still carry it by hand.
The promise: a new service for the same 5 steps
Now I want to call back a promise, because this module is where I keep it.
Do you remember reason number 2, from lesson 5? Your script is wired to your setup. Every other app needs the glue written again. M jobs, N apps, and you write M×N pieces of glue.
In lesson 6 you watched that become M+N, with 2 servers that other people wrote. And in lesson 13 the server in the middle was yours.
But every time since then, you added a tool. read_doc. edit_doc. Remember. find_note. All of them talk to the same 2 places, your Drive and your memory file.
So here is the promise, in plain words. A whole new service, not a new tool. A different company, a different web address, a different login. And it costs the same 5 steps.
That is the strongest claim in this course. And next lesson I do not claim it. I make it, with the clock running.
What module 4 adds and what each part needs
So what does module 4 add? 3 things, and I want to be straight about what each one needs.
First, a second service. Substack. Scribe gets 2 new tools. One reads the newest posts on any Substack, and it needs no login at all. The other sends a finished draft from your Drive into your Substack, as a draft post.
The read half needs nothing. No account, no key, no cookie. The write half needs a Substack of your own, and 1 cookie from your browser, which we handle like a password.
Second, off the laptop. Today Claude Desktop starts your server on your own machine, and the 2 of them talk through a pipe. In lesson 27 the pipe becomes a web address, and in lesson 28 the server runs on a free host, so it is up while your laptop is shut. That part needs a GitHub account and a free hosting account.
Third, the registry. There is a public list of MCP servers now. It gets 1 minute, and a note in your checkpoint, because for Scribe the right move is to not list your address at all. I will tell you why in lesson 28.
And if you stop after lesson 26, you still have a working server with 7 tools. Lesson 28 is a bonus, not a wall.
What publish draft really does
Now 1 thing about the word publish, before you hear the tool's name.
The tool is called publish draft. And it does not press Publish.
It makes a draft post inside your Substack, with your title and your headings, and it hands you the link. You open it, you read it, and you press the button yourself.
I did that on purpose. A tool that can send an email to every subscriber you have, with no question asked, is the quiet mistake from lesson 16 again. Only bigger, and with no undo.
So the last click stays yours. The last manual step becomes 1 click instead of a copy and a paste and a fix. That is the whole trade.
Grab the checkpoint, and what is next
One thing to do before the next lesson. Grab the module 4 checkpoint.
It holds Scribe exactly as module 3 left it, with the guard and the memory working. It has a requirements file with the 4 lines the host will need. It has a proof script for lesson 26, and the registry notes for lesson 28.
So where does our map stand at the end of this lesson?
Still 13 boxes lit, and the 3 at the bottom are still dark. But you know what each one costs, and you know which ones are free.
Next lesson is run number 5 of the 5 steps. A whole new service, and I want you to watch the clock.
Bye now, and I will see you in the next lesson.
