MCP config starter for Cursor, Claude Code and Codex + safety checklist

Copy-paste MCP configs for Supabase and GitHub in Cursor, Claude Code and Codex, plus a checklist to vet any MCP server before you connect it.

· By Codema Editorial

Free account required

The same two servers, Supabase (read-only) and GitHub, set up for three tools. Tokens stay in environment variables.

Preview: .mcp.json

{
  "mcpServers": {
    "supabase": {
      "type": "http",
      "url": "https://mcp.supabase.com/mcp?project_ref=YOUR_PROJECT_REF&read_only=true"
    },
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/",
      "headers": {
        "Authorization": "Bearer ${GITHUB_PAT}"
      }
    }
  }
}

What's inside

  • .cursor/mcp.json for Cursor
  • .mcp.json for Claude Code
  • .codex/config.toml for Codex
  • MCP-SAFETY-CHECKLIST.md: vet, pin, scope and review servers

How to use it

  1. Copy the file for your tool into your project.
  2. Replace YOUR_PROJECT_REF with your Supabase project ref.
  3. Export a fine-grained GitHub token: export GITHUB_PAT=...
  4. Sign in and check: /mcp in Claude Code, codex mcp list in Codex, MCP Logs in Cursor.

Who it's for

Builders connecting their first MCP servers, or tightening the ones they have.

Keep reading

Keep reading

Newsletter

The Codema publication. Consent is required. You are not subscribed until you confirm from the email, and nothing is stored if email delivery is not connected.