How to Connect Supabase to an AI Agent
Auth setup
1. claude mcp add --transport http supabase https://mcp.supabase.com/mcp. 2. First use triggers browser OAuth — log into Supabase. 3. Grant access. Done. No token copying needed.
Key facts
| Base URL | https://<project_ref>.supabase.co |
|---|
| API version | v1 |
|---|
| Auth | OAuth 2.0 via hosted MCP server (primary, recommended). Browser redirect to Supabase login — no token management needed. Alternative: Personal access token for local npx setup. |
|---|
| Token URL | https://<project_ref>.supabase.co/auth/v1/token |
|---|
| Scopes | anon,authenticated,service_role |
|---|
| Request body | application/json |
|---|
| Pagination | Range header: Range: 0-9 (first 10 rows). Response includes Content-Range: 0-9/42 for total. |
|---|
| Rate limit | Follows Supabase API rate limits. Database queries: depends on project tier (free: 500 connections, pro: higher). Management API: standard rate limits apply. |
|---|
| Error format | PostgREST: { "code": "PGRST116", "message": "...", "details": "...", "hint": "..." }. Auth: { "error": "invalid_grant", "error_description": "..." }. Always check status + body.code. |
|---|
Key endpoints
| Method | Path | Description |
|---|
POST | /auth/v1/signup | |
POST | /auth/v1/token?grant_type=password | |
GET | /rest/v1/<table> | |
POST | /rest/v1/<table> | |
PATCH | /rest/v1/<table>?id=eq.<id> | |
DELETE | /rest/v1/<table>?id=eq.<id> | |
POST | /storage/v1/object/<bucket>/<path> | |
POST | /functions/v1/<name> | |
Quickstart
# Hosted MCP (recommended):
claude mcp add --transport http supabase https://mcp.supabase.com/mcp
# Then ask Claude:
# 'List my Supabase projects'
# 'Create a users table with email, name, and created_at'
# 'Run SELECT * FROM users LIMIT 10'
# 'Generate TypeScript types for my schema'
Agent pitfalls & tips
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-07-06. Specs change — verify against the official docs before production use.
Frequently Asked Questions
What is Supabase's AEO score?
▼
Supabase has an AEO score of 0.70 and is rated A (Functional agent integration). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Supabase AI-agent-ready?
▼
Supabase is currently connectable for AI agent use. Third-party MCP integrations are available for this service. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Supabase compare to other Database services?
▼
In the Database category, Supabase is rated A. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Supabase compares.
How can I integrate Supabase with an AI agent?
▼
The fastest way to integrate Supabase with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Supabase?
▼
OAuth 2.0 via hosted MCP server (primary, recommended). Browser redirect to Supabase login — no token management needed. Alternative: Personal access token for local npx setup. Setup: 1. claude mcp add --transport http supabase https://mcp.supabase.com/mcp. 2. First use triggers browser OAuth — log into Supabase. 3. Grant access. Done. No token copying needed.
What are Supabase's API rate limits?
▼
Follows Supabase API rate limits. Database queries: depends on project tier (free: 500 connections, pro: higher). Management API: standard rate limits apply.