GraphQL integration
Supabase GraphQL GraphQL integration for Draftbit
GraphQL over your Supabase Postgres (pg_graphql)
Build a working app with Supabase GraphQL
- Build a mobile app with Draftbit and Supabase
A private task app with sign-in, photos, and live updates. Follow the prompts and code, then verify the result in your app.
What is Supabase GraphQL?
Build a task app with Supabase Auth, Postgres, Storage, and Realtime. Use the project's publishable key and the signed-in user's session in the app, then enforce ownership with Row Level Security. MCP tools help the agent inspect a project while it builds; they don't establish the mobile user's identity or replace database policies.
Use Supabase GraphQL with Draftbit
- Create and read tasks owned by the signed-in user.
- Protect database rows and stored files with ownership policies.
- Refresh a task list when authorized data changes.
More ways to connect Supabase
Need a REST API connection instead? Use the Supabase REST API integration .
Want AI agents to query and act on Supabase while you build? Use the Supabase MCP server .
Example
supabase-graphql-query.graphql # Example query against Supabase GraphQL
query GetItems {
items(limit: 10) {
id
name
createdAt
}
}Use cases
- Power a mobile app with a hosted database and APIs
- Add search, filtering, and pagination to a list-driven feature
- Read and write app data without managing your own server
Authentication
Add any required auth headers when you connect Supabase GraphQL. Headers are stored per app and applied to every operation.
Use Supabase GraphQL in a Draftbit app today
Use Draftbit to build your app, configure Supabase GraphQL, and test the feature before publishing.
Frequently asked questions
How does this service fit into the app?
Build a task app with Supabase Auth, Postgres, Storage, and Realtime. Use the project's publishable key and the signed-in user's session in the app, then enforce ownership with Row Level Security. MCP tools help the agent inspect a project while it builds; they don't establish the mobile user's identity or replace database policies.
Does adding an integration finish the runtime setup?
No. Follow the linked walkthrough to install the SDK or build the backend and the app requests. The tools the agent uses while building don't replace sign-in and authorization in the app itself.
Where should I start?
Open the guide above, create a separate test project, and use its prompts and code to build one working feature. A template gives you a starting interface; you'll still connect the service yourself.
What should I verify before publishing?
The successful flow, a failed request, sign-out, and what a second user can see. Check that secret keys stay on the backend. For payments, run the provider's real sandbox flow in a native build too.
