Most people starting out with Claude connect it to nothing and wonder why they're not getting anywhere. Here are the five MCP services I use every day — each one solves a different pain point.
What is an MCP?
MCP stands for Model Context Protocol . Translation: a standardised bridge between Claude and an external service. With that bridge, Claude can commit to GitHub or deploy a site directly. You stop copy-pasting between tabs.
Without MCP you talk to Claude and execute everything yourself. With MCP, Claude executes.
GitHub
Link: github.com
GitHub stores your codebase in the cloud. Even if you don't code yourself:
Connecting multiple services only works in the cloud, not locally
Roll back versions instead of collecting final_final_v2.zip files
Claude reads, writes and merges straight from the chat
Your first step: GitHub account → create an empty repo → activate the MCP connector in Claude
Supabase
Link: supabase.com
Database, auth and file storage in one tool. You need this as soon as you:
Want to create users or build logins
Need to store, query or search data
Manage sessions, orders or content
Your first step: supabase.com → create project → paste the API keys into the Claude MCP
Vercel
Link: vercel.com
Vercel hosts whatever Claude builds — prototype, landing page or full app:
Push to GitHub → Vercel deploys automatically
A preview URL for every branch (so every variant is live for you to check)
Domains, env variables and logs in one dashboard
Your first step: vercel.com → connect to GitHub → import your first repo
Figma
Link: figma.com
Figma is the design tool. You don't need design skills:
Buy or grab free templates (there's a template for everything)
Claude pulls fonts, colours and spacing straight from the Figma file
You describe the layout, Claude builds it with the right tokens
Your first step: figma.com → find a template → give Claude the Figma link
Notion
Link: notion.so
Notion is your knowledge base and team tool in one. In a dev context that means:
Specs, roadmaps, briefs — all in one place, readable by Claude
Non-coders on the team see what you're working on
Claude writes notes itself, ticks off tasks, updates status
Your first step: notion.so → workspace → authorise the MCP connector
How to connect them to Claude
In Claude Desktop or Cowork: Settings → Connectors → "Add Connector" . Pick the service, paste an API token or log in, done. Next chat, Claude has the tools available — you don't have to wire them up every time.
The order I recommend:
GitHub first — without a repo, nothing happensVercel right after — so you can deploy live immediatelySupabase once data comes into playFigma once it needs to look goodNotion last , when you need documentation or work with a team You don't have to connect all five at once. But building a prototype completely without this layer costs you more time than the setup ever could save.
