Lark AgentCore Gateway Interceptor Server vs Supabase
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
Enables Bedrock agents to act as a Lark user, performing document operations (list, create, edit, delete) and identity verification via Lark's REST API, with pe
Comparison
| Feature | Lark AgentCore Gateway Interceptor Server | Supabase |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | — |
| Rating | — | — |
| Verified | — | |
| Hosted | Hosted | — |
| Tools | — | 4 |
| Category | development | development |
| Author | aws-samples | Supabase |
| Repo | aws-samples/sample-lark-identity-on-agentcore-interceptor | supabase-community/supabase-mcp |
When to pick Lark AgentCore Gateway Interceptor Server
Enables Bedrock agents to act as a Lark user, performing document operations (list, create, edit, delete) and identity verification via Lark's REST API, with per-user credential injection through a Gateway Interceptor.
When to pick Supabase
Full Supabase project access — query tables, inspect auth users, manage storage. Perfect companion for indie-hacker apps.
Looking for something else? Browse all MCPs or check trending this week.