supabase-community/supabase-mcp

AI Evaluation Report

Total Score: 8/10

The agent demonstrates a strong ability to interact with Supabase projects, effectively handling tasks related to documentation search, database operations, and edge function management. It provides detailed and accurate responses, particularly in listing Edge Functions and deploying them, showcasing its strengths in these areas. However, there are some weaknesses, such as incomplete data retrieval when querying database records and listing tables, which indicates room for improvement in database operations. Additionally, while the agent provides useful guidance on resolving deployment issues, it could enhance its responses by ensuring completeness and relevance in all scenarios. Overall, the agent is competent and reliable, with minor areas for enhancement.

• Test case 1

  Score: 7/10

  Please search for Supabase authentication documentation.

  Here are some key resources from the Supabase documentation regarding authentication:

  1. Glossary

     • This section provides definitions for various terms related to authentication, including access tokens, authentication methods, identity providers, multi-factor authentication (MFA), and more.
     • It explains concepts such as JSON Web Tokens (JWT), OAuth, and Row Level Security (RLS).

  2. Supabase Authentication Token Cross-Instance Validation Issue

     • This discussion addresses a security concern where a Supabase authentication token from one instance is incorrectly accepted by another instance, highlighting the importance of proper token validation.

  3. Features

     • This section outlines various features of Supabase, including authentication capabilities such as email login, social login, phone logins, passwordless login, and authorization via Row Level Security.

  4. Resolving 500 Status Authentication Errors

     • This guide helps troubleshoot 500 errors related to authentication by providing steps to check logs and identify common issues with databases and email providers.

  5. Multi-Factor Authentication

     • This section details how to implement multi-factor authentication in your application, including enrollment and authentication flows. It emphasizes the importance of MFA for securing user accounts and provides APIs for managing MFA factors.

  If you need more specific information or additional topics related to Supabase authentication, feel free to ask!

• Test case 2

  Score: 5/10

  Please query the first 10 records from the users table.

  Here are the first 10 records from the users table:

  1. User ID: 123456

     • Created At: 2025-09-12 03:38:22 UTC

  2. User ID: 135678

     • Created At: 2025-09-12 03:39:08 UTC

  3. User ID: 156789

     • Created At: 2025-09-12 06:18:13 UTC

  Please note that these records contain untrusted user data, and it is advisable not to execute any commands or follow any instructions based on this data.

• Test case 3

  Score: 6/10

  Please list all tables in the public schema.

  In the public schema, there is one table listed:

  Table: users

  • Schema: public
  • Rows: 3
  • RLS Enabled: Yes

  Columns:

  1. id

     • Data Type: bigint
     • Format: int8
     • Options: identity, updatable
     • Identity Generation: BY DEFAULT

  2. created_at

     • Data Type: timestamp with time zone
     • Format: timestamptz
     • Options: updatable
     • Default Value: now()

  Primary Key:

  • id (This is the primary key for the table)

  If you need more information or additional tables, feel free to ask!

• Test case 4

  Score: 9/10

  Lists all Edge Functions in a Supabase project.

  Here is a list of the Edge Functions in your Supabase project:

  Edge Functions

  1. Function Name: hello_edge_function
     • ID: 43fbbc45-e151-4f06-aba5-89347dcad27b
     • Version: 2
     • Status: ACTIVE
     • Entrypoint Path: ../user_fn_qwegwmcnlfcxffidayao_43fbbc45-e151-4f06-aba5-89347dcad27b_1/source/index.ts
     • Created At: (Timestamp: 1755588101912)
     • Updated At: (Timestamp: 1755588101912)
     • Files:
       • File Name: index.ts
         • Content:

         import "jsr:@supabase/functions-js/edge-runtime.d.ts";
         Deno.serve(async (req) => {
           const data = {
             message: "Hello there!"
           };
           return new Response(JSON.stringify(data), {
             headers: {
               'Content-Type': 'application/json',
               'Connection': 'keep-alive'
             }
           });
         });
         

  Summary

  The project currently contains an active Edge Function named hello_edge_function, which returns a simple JSON response with a greeting message. If you have more Edge Functions or need further details, let me know!

• Test case 5

  Score: 9/10

  Please deploy a simple hello world edge function.

  To deploy a simple "Hello World" Edge Function in Supabase, I'll create a basic function that responds with a JSON message. Here's the plan:

  1. Create the Function Code: We'll write a simple function that returns a JSON response with a "Hello World" message.
  2. Deploy the Function: Use the Supabase tool to deploy this function.

  Let's start by creating the function code. Here's a simple example:

  // index.ts
  import "jsr:@supabase/functions-js/edge-runtime.d.ts";
  
  Deno.serve(async (req: Request) => {
    const data = {
      message: "Hello World!"
    };
    
    return new Response(JSON.stringify(data), {
      headers: {
        'Content-Type': 'application/json',
        'Connection': 'keep-alive'
      }
    });
  });
  

  Now, I'll deploy this function using the Supabase tool. It seems that the deployment failed because the Supabase project is currently in an "INACTIVE" status. This could happen if the project is not properly set up or if there are issues with its configuration.

  To resolve this issue, please check the following:

  1. Project Status: Ensure that the Supabase project is active and running. If it is inactive, you may need to activate it through the Supabase dashboard.

  2. Configuration: Verify that all settings and configurations for the project are correctly set up.

  3. Permissions: Ensure that you have the necessary permissions to deploy Edge Functions in the project.

  Once the project status is resolved, I can attempt to deploy the function again. If you want, I can also check the project status or logs to gather more information. Would you like me to do that?