Vovy adds MCP servers to Claude Code so it can read your database, GitHub issues or docs directly, scoped to the project and with safe permissions.
Hook up the Supabase and GitHub MCP servers to Claude Code for this project
How it works
- Pick the servers you need: MCP, Model Context Protocol, is a plug that lets an AI tool talk to another service. Vovy suggests servers based on your stack.
- Add them with claude mcp add: Vovy runs claude mcp add with project scope, which writes a .mcp.json file so the setup travels with the repo.
- Sign in to each service: Inside Claude Code, Vovy runs /mcp. Each service opens a browser login, and you approve access yourself.
- Limit what it can touch: Vovy recommends read-only mode or a dev project for database servers, so Claude Code cannot change production data by accident.
- Test each connection: Vovy asks Claude Code to list your tables and open issues, and shows a card of each server, its status and what it can do.
What you provide
- Claude Code installed
- Accounts for the services you connect
What you get
- MCP servers connected to Claude Code
- A project .mcp.json file
- Read-only access where it matters
- Each connection tested
FAQ
Is it risky to give AI access to my database?
It can be. Point it at a development project or use read-only mode, and keep Claude Code's approval prompts on for writes.
Will teammates get the same servers?
Project-scoped servers live in .mcp.json in the repo. Each person still signs in with their own account.
Do MCP servers cost money?
Most are free to connect. You still pay for whatever the underlying service charges.
Related tasks
All tasks