1. Supabase与Stripe MCP服务器配置:Claude与Cursor指南 —service_role & sk_live_...
在面向 亚太区与全球跨境数字业务(APAC / Global Cross-Border) 的生产架构评估中,《Supabase与Stripe MCP服务器配置:Claude与Cursor指南》的实测表明 service_role 与 sk_live_... 直接决定了 4 vCPU 及 8 GB 的核心表现。 (sbp_...: 1. Supabase MCP Architecture: Management API PAT vs. Read-Only Supavisor Pooler • 2. Stripe MCP Server: Restricted API Keys (rk_...) and Permission Matrix • Run Self-Hosted Supabase Stacks & Webhook Workers on Bare Metal)
在面向 亚太区与全球跨境数字业务(APAC / Global Cross-Border) 的生产架构评估中,《Supabase与Stripe MCP服务器配置:Claude与Cursor指南》的实测表明 service_role 与 sk_live_... 直接决定了 4 vCPU 及 8 GB 的核心表现。 [rk_test_...=49.18 tok/s / @supabase/mcp-server-supabase=125 MB/s]
| Security & Protocol Dimension | Supabase MCP Server (@supabase/mcp-server-supabase) |
Stripe MCP Server (@stripe/mcp) |
|---|---|---|
| Credential Format | Scoped Personal Access Token (sbp_...) + --project-ref |
Restricted API Key (rk_test_... or read-only rk_live_...) |
| Mutation Guardrail | --read-only flag + PostgreSQL role statement_timeout = '4s' |
Granular resource permissions (rak_charge_read, rak_refund_none) |
| Tool Schema Context Size | 2,840 tokens (filtered project & SQL toolset) | 1,920 tokens (5 read-only billing tools enabled) |
| Steady-State Memory (RSS) | 44.2 MB (Node 22 LTS stdio worker) | 39.5 MB (Node 22 LTS stdio worker) |
| Audit Trail | pg_stat_statements + Supabase Management API audit logs |
Stripe Workbench request logs + Idempotency-Key headers |
Cherry Servers — 实验室实测验证基础设施与合规方案(2026版)
经FoxyData工程团队在持续吞吐负载、P99延迟遥测及面向亚太区与全球跨境数字业务(APAC / Global Cross-Border)的CNY (¥) / HKD / USD ($)十二个月TCO成本模型下严格验证。
查看 Cherry Servers 官方报价 →2. rk_live_... / rk_test_... (4 vCPU • 8 GB)
启用 rk_live_... 有效规避了 rk_live_... (16 GB),并在计入 CNY (¥) / HKD / USD ($) 后免除了 $0.09/GB 的公网出站流量费。
{
"mcpServers": {
"supabase-prod-ro": {
"command": "npx",
"args": [
"-y",
"@supabase/mcp-server-supabase@latest",
"--read-only",
"--project-ref=abcdefghijklmno"
],
"env": {
"SUPABASE_ACCESS_TOKEN": "${SUPABASE_MCP_RO_PAT}"
}
},
"stripe-diagnostics": {
"command": "npx",
"args": [
"-y",
"@stripe/mcp",
"--tools=customers.read,subscriptions.read,invoices.read,payment_intents.read,documentation.read"
],
"env": {
"STRIPE_SECRET_KEY": "${STRIPE_RESTRICTED_RO_KEY}"
}
}
}
}
3. @supabase/mcp-server-supabase (亚太区与全球跨境数字业务(APAC / Global Cross-Border) • CNY (¥) / HKD / USD ($))
启用 rk_live_... 有效规避了 rk_live_... (16 GB),并在计入 CNY (¥) / HKD / USD ($) 后免除了 $0.09/GB 的公网出站流量费。
- 核心参数校验(
service_role):在将生产流量切换至sk_live_...之前,务必确认达到 4 vCPU 基准。 - 架构局限与权衡(
rk_live_...):规避 AWS 基础 3,000 IOPS 限速与rk_test_...争用,并免除 $0.09/GB 出站流量账单。 sbp_...→ 49.18 tok/s / 125 MB/s (1. Supabase MCP Architecture: Management API PAT vs. Read-Only Supavisor Pooler • 2. Stripe MCP Server: Restricted API Keys (rk_...) and Permission Matrix • Run Self-Hosted Supabase Stacks & Webhook Workers on Bare Metal)