Out of the box, Claude Code works inside your files and your terminal. These four connect it to the parts it cannot see: your database, your deployments, a planner that keeps it working, and a browser it can test in. Install one, check it works, then move to the next.
Read online: https://abhibuildsit.pages.dev/coding/
Supabase: let Claude see your database
Claude stops guessing your tables and columns. It can read the real schema, write migrations, check logs and generate types, so database code works the first time.
How to do it
- Open a terminal in your project folder.
- Add the server:
claude mcp add --scope project --transport http supabase "https://mcp.supabase.com/mcp?project_ref=<your-project-ref>&read_only=true" - Find your project ref in the Supabase dashboard address bar, the part after project/ in:
supabase.com/dashboard/project/<project-ref> - Run
claude, type/mcp, select supabase and choose Authenticate. Sign in in the browser and pick the organisation that holds the project. - Keep
read_only=trueuntil you trust it, and point it at a development project, never production.
Prompt for Claude
Use the Supabase tools to list every table in my project with its columns, types and foreign keys. Then draw the relationships as a simple text diagram, and point out any table that has no primary key or no row level security.
Check it worked
Type /mcp in Claude Code: supabase shows as connected. Ask the prompt above, and the table names in the answer match the Table Editor in your Supabase dashboard.
Vercel: deploy and read the logs from chat
When a deploy fails, Claude can open the build logs itself, find the error and fix it, instead of you copying logs back and forth.
How to do it
- In your project folder, run:
claude mcp add --transport http vercel https://mcp.vercel.com - Start
claude, type/mcp, select vercel and sign in to your Vercel account in the browser. - Approve the connection for the team that owns your project.
Prompt for Claude
Use the Vercel tools to find my most recent deployment for this project. If it failed, read the build logs, explain the error in one paragraph and fix it in the code. If it succeeded, tell me the live URL and how long the build took.
Check it worked
Ask Claude to list your Vercel projects. The list matches what you see on vercel.com/dashboard.
oh-my-claudecode: a team of agents that keeps going
Big jobs stall when Claude stops to ask what next. oh-my-claudecode adds planning, autopilot and team modes, so one request is split into steps, run, checked and fixed without you nudging it.
How to do it
- Inside Claude Code, type:
/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode - Then, as a separate message:
/plugin install oh-my-claudecode(pasting both lines at once fails). - Run
/omc-setuponce to finish the setup. - Start with a small job, for example:
/autopilot "add a dark mode toggle to the settings page" - Use
/teamfor bigger work, for example:/team 3:executor "fix all TypeScript errors"
Prompt for Claude
/autopilot "Read this project, list the five most important bugs or missing tests, fix the top two, run the tests, and write a short summary of what changed and why."
Check it worked
Type / in Claude Code: commands such as /autopilot and /team appear in the list. A run ends with a summary of the steps it planned and checked.
Chrome DevTools MCP: let Claude test in a real browser
Claude can open your site in Chrome, click through it, read console errors and network requests, and run a performance trace. It sees what your users see, not just the code.
How to do it
- Make sure Node.js (LTS) and the current Chrome are installed.
- Inside Claude Code, type:
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp - Then:
/plugin install chrome-devtools-mcp@chrome-devtools-plugins - Or add it as a plain server from the terminal:
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest - Restart Claude Code so the new tools load.
Prompt for Claude
Start my dev server, open the home page in Chrome with the DevTools tools, and check it the way a picky user would: console errors, failed network requests, layout at phone width, and the LCP time from a performance trace. List every problem with the file to fix, then fix the worst one.
Check it worked
Ask: "Check the performance of https://developers.chrome.com". A Chrome window opens, and Claude reports real numbers such as LCP from the trace.