How to integrate Supabase MCP with Hermes

Connect Hermes to Supabase MCP. List all projects and their databases, deploy edge function from repo branch, and more using natural language, with authentication handled for you.

Supabase MCP logoSupabase MCP
Dcr Oauth

Supabase MCP is Supabase's hosted MCP server for managing projects, databases, edge functions, storage, and workflows. Use it to manage Supabase resources and development workflows from a single hosted control plane.

32 Tools

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Supabase account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Supabase MCP with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,500+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Supabase with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Supabase

Ask your agent to connect to Supabase, or simply request any Supabase-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Supabase connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Supabase or request any Supabase-related task. It will prompt you to authenticate and authorize access.

5. Done!

What is the Supabase MCP server, and what's possible with it?

The Supabase MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Supabase account. It provides structured and secure access so your agent can perform Supabase operations on your behalf.

Way Forward

With Supabase connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

TOOLS

Supported Tools

Every Supabase MCP action and event your agent gets out of the box.

Apply migration

Applies a migration to the database.

Confirm cost

Ask the user to confirm their understanding of the cost of creating a new project or branch.

Create branch

Creates a development branch on a Supabase project.

Create project

Creates a new Supabase project.

Delete branch

Deletes a development branch.

Deploy edge function

Deploys an Edge Function to a Supabase project.

Execute sql

Executes raw SQL in the Postgres database.

Generate typescript types

Generates TypeScript types for a project.

Get advisors

Gets a list of advisory notices for the Supabase project.

Get cost

Gets the cost of creating a new project or branch.

Get edge function

Retrieves file contents for an Edge Function in a Supabase project.

Get organization

Gets details for an organization.

Get project

Gets details for a Supabase project.

Get project url

Gets the API URL for a project.

Get publishable keys

Gets all publishable API keys for a project, including legacy anon keys (JWT-based) and modern publishable keys (format: sb_publishable_.

Get storage config

Get the storage config for a Supabase project.

List branches

Lists all development branches of a Supabase project.

List edge functions

Lists all Edge Functions in a Supabase project.

List extensions

Lists all extensions in the database.

List migrations

Lists all migrations in the database.

List organizations

Lists all organizations that the user is a member of.

List projects

Lists all Supabase projects for the user.

List storage buckets

Lists all storage buckets in a Supabase project.

List tables

Lists all tables in one or more schemas.

Merge branch

Merges migrations and edge functions from a development branch to production.

Pause project

Pauses a Supabase project.

Query logs

Runs a custom read-only ClickHouse SQL query against a Supabase project's unified logs stream, for filtering, aggregating, or joining across log fields more precisely than a simple per-service log dump.

Rebase branch

Rebases a development branch on production.

Reset branch

Resets migrations of a development branch.

Restore project

Restores a Supabase project.

Search docs

Search the Supabase documentation using GraphQL.

Update storage config

Update the storage config for a Supabase project.

FRAMEWORKS

How to build Supabase MCP Agent with another framework

FAQ

Frequently asked questions

With a standalone Supabase MCP server, the agents and LLMs can only access a fixed set of Supabase tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Supabase and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Hermes fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Supabase tools.

Yes, absolutely. You can configure which Supabase scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Supabase data and credentials are handled as safely as possible.

Start with Supabase MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Supabase MCP tool your agent needs.Free to start.

Start building