Dataset to Postgres, Supabase & MySQL (Database Push)

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.0Updated Oct 24, 2026

Push rows from a dataset, file or Google Sheet into a Postgres, Supabase, Neon or MySQL table.

The publisher's own server: Supabase

VerifiedStreamable HTTPWeb executableDatabasesData & Analytics

Overview

AI-generated overview

Apify-hosted MCP server that lets an assistant push rows from a dataset, file or Google Sheet into a Postgres, Supabase, Neon or MySQL table.

What you can do
  • Push rows from a dataset, file or Google Sheet into a target database table.
  • Load data into Postgres, Supabase, Neon or MySQL destinations.
  • Run the transfer as an Apify actor through the hosted MCP endpoint rather than local code.
When to use it
Useful when you already have tabular data in a dataset, file or Google Sheet and want an assistant to load it into a relational database table without writing a custom import script.
Requirements
A remote MCP endpoint at mcp.apify.com with OAuth authentication; an Apify API token sent as a Bearer token in the Authorization header. A reachable Postgres, Supabase, Neon or MySQL target and its connection details are needed for the push itself.
Before you install
The Authorization header carries an Apify API token, and runs are billed per event to your Apify account, so usage costs money. The server writes rows into your database, so point it at the intended table and review what it inserts. Database connection details are passed to a third-party Apify service.

Installation

In SourceWeft

  1. Open Dataset to Postgres, Supabase & MySQL (Database Push) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Nero-Engine%2Fdataset-to-database/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dataset-to-postgres-supabase-mysql-datab": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/dataset-to-database"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Supabase integrations