MCP Servers
6 tools
What is an MCP server?
Your agent can only work with what it can reach. An MCP server connects it to one more thing, such as your database, your GitHub repos or a real browser, so it can look things up and take action there instead of asking you to copy and paste. MCP is the shared standard, so one server works with Claude Code, Cursor, Codex and most other agents.
Remote servers
A web address you add to your agent, then sign in with your account in the browser. Nothing to install. Most services you already use offer one.
Local servers
Run on your own computer with one command, usually starting npx. Used for things on your machine, such as controlling a browser.
Staying safe
A server acts with your permissions. Use read-only mode where it exists, point it at a test project rather than live data, never paste API keys into chat, and only add servers from companies you trust.
Which one do I need? Add a server for each service your project already uses, such as your database or where you deploy. Start with one, check what your agent does with it, then add the next.
GitHub MCP Server
Let your agent work with repos, issues, PRs and Actions.
Open sourceOfficialRemoteRuns locallySign inSupabase MCP Server
Let your agent query and migrate your Supabase project.
FreeOfficialRemoteSign inRead-only mode
