Vibe Coder · Unit 11: Connectors, MCP and Workflows · Project
Milestone 11 of 16
An automated workflow
Your app connected to a tool you already use.
One product, built in sixteen steps
Vibe Coder has one project. You pick an idea in Unit 1 and every unit adds a piece to it, until Unit 16 launches it. A product is more useful when it reaches the tools people already have open. This milestone connects your app to one of them, and makes something happen without you starting it.
- 1Your builder’s kitA one-line product idea, your role, and five working accounts.
- 2A fact-checked product briefOne page on your idea, tested against how the models really behave.
- 3Your product project in ClaudeA project with instructions and files, and your first real piece of work from it.
- 4A brand kit and research fileA name, images and market research for your product, with a second opinion.
- 5Your prompt libraryThe prompts you will reuse to build the product, each one tested.
- 6Your product specThe problem, the people, the first version and how you will measure it.
- 7A clickable prototypeA version people can click through, shown to three of them.
- 8The first working versionYour app running on your computer, built with Claude Code.
- 9Your Claude Code setupProject instructions, a custom command and a skill made for your app.
- 10One AI featureA feature in your app that calls a model, with its key kept safe.
- 11An automated workflowYour app connected to a tool you already use.
- 12Sign-in and saved dataAccounts and a database behind your app.
- 13A tested, locked-down appEvery flow checked, and each person able to see only their own data.
- 14A launch videoThirty to sixty seconds, with voice, music and sound.
- 15Your app, liveOnline at its own address, updating every time you save.
- 16Your launched productThe finished product, in front of people, with a page that shows your work.
You start with
One AI feature
A feature in your app that calls a model, with its key kept safe.
Milestone 10Your product gains
A connection to a tool you already use
That makes 11 of 16 pieces in place.
Your role
The steps change with your role. Choose yours to see your version of this milestone.
Start with this prompt
Paste it into Claude or ChatGPT, or into Claude Code once you are building. Fill in the parts in square brackets with your own product.
My app does this: [one line]. The tools I already use every day are: [list them] Suggest three small workflows that would connect my app to one of those tools. For each, say what starts it, what it does, and what a person would have to approve. Work with me one step at a time. Ask me one question, wait for my answer, then go on. Do not write the finished thing for me: show me a draft, tell me what is weak about it, and let me decide. I will pick the smallest one that would save me real time.
Build it step by step
6 steps, one from each lesson of the unit. Do each step after its lesson. A box you tick here is ticked in the lesson too.
Step 1 of 6 · from the lesson Connectors and apps
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepAn automated workflow Map and connect your tools
List the tools your product’s work touches, mark where you copy between them, and connect the two that would save the most. Use each once on a real task.
Done when
These connections feed the workflow you build in this unit.
Step 2 of 6 · from the lesson What MCP is
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepAn automated workflow Draw your MCP map
For the connections you have, write down which are remote and which are local, and for each list two tools it gives the assistant. Add the map to "My build".
Done when
You will use one of these servers directly in the next lesson.
Step 3 of 6 · from the lesson Using an MCP server
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepAn automated workflow Use a server on real work
Add one MCP server to Claude Code or the Claude app for a system your product uses. Complete one read task and one write task with it.
Done when
This server is a building block of your workflow.
Step 4 of 6 · from the lesson Building an MCP server
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepAn automated workflow Build a one-tool server
Write an MCP server with one read-only tool over your product’s data, with input validation and per-user authorisation. Test it in the inspector and use it from Claude Code.
Done when
This server is part of your engineer capstone.
Step 5 of 6 · from the lesson Scheduled workflows
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepAn automated workflow Schedule your first workflow
Write and schedule one weekly task for your product, such as a summary of new feedback or sign-ups, using a connection you set up. Run it once by hand and read the result.
Done when
Your automated workflow is running. Role lessons extend it for your kind of work.
Step 6 of 6 · from the lesson A CI workflow
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepAn automated workflow Add CI to your repository
Add a workflow that runs your checks and an agent review on pull requests, and protect main. Prove it with a pull request that fails, then passes.
Done when
Vercel will add preview deployments to the same pull requests in Unit 15.
When it is done
Every box above is ticked, and you can show the result to someone who has not seen it before. Then move on: milestone 12 is sign-in and saved data.