Memory and database access for your AI assistant

The scenario connects your assistant to a Supabase database: it searches your knowledge base and keeps records itself — tasks, messages, statuses, notes.

  • The assistant remembers context between chats
  • Searches answers in your knowledge base
  • Keeps tasks, messages and notes itself
  • Reads and updates data in Supabase
MCP ServerSupabase Vector StoreEmbeddings OpenAISupabase Tool
Connect Supabase and goScriptera

How it works

To connect MCP Server and Supabase Vector Store, you don't need a developer: a ready-made scenario links them in minutes.

  1. Starts when: MCP_SUPABASE
  2. Then: RAG
  3. Then: Embeddings OpenAI
  4. Then: DELETE_ROW_INSCRICOES_CURSOS
  5. Then: GET_ROW_AGENT_MESSAGE
  6. Then: CREATE_ROW_AGENT_MESSAGE
  7. Then: DELETE_ROW_AGENT_MESSAGE
  8. Then: UPDATE_ROW_AGENT_MESSAGE
  9. Then: GET_MANY_ROW_AGENT_MESSAGE
  10. Then: CREATE_ROW_AGENT_TASKS
  11. Then: GET_ROW_AGENT_TASKS
  12. Then: DELETE_ROW_AGENT_TASKS
  13. Then: UPDATE_ROW_AGENT_TASKS
  14. Then: GET_MANY_ROW_AGENT_TASKS
  15. Then: CREATE_ROW_AGENT_STATUS
  16. Then: GET_ROW_AGENT_STATUS
  17. Then: DELETE_ROW_AGENT_STATUS
  18. Then: UPDATE_ROW_AGENT_STATUS
  19. Then: GET_MANY_ROW_AGENT_STATUS
  20. Then: CREATE_ROW_AGENT_KNOWLEDGE
  21. Then: GET_ROW_AGENT_KNOWLEDGE
  22. Then: UPDATE_ROW_INSCRICOES_AGENT_KNOWLEDGE
  23. Then: GET_MANY_ROW_AGENT_KNOWLEDGE

You can launch this MCP Server + Supabase Vector Store integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios