Scribase

com.scribasePublished by scribase.comOfficial publisherv1.0.0Updated Oct 26, 2026

Supabase-compatible Postgres for agents: projects, branches, SQL, auth, storage, email.

VerifiedStreamable HTTPWeb executableDatabasesCloud & Infrastructure

Overview

AI-generated overview

Scribase is a remote MCP server offering Supabase-compatible Postgres for agents: projects, branches, SQL, auth, storage and email.

What you can do
  • Manage Postgres projects and branches through the hosted service
  • Run SQL against those databases
  • Work with authentication and user management
  • Handle file storage and email features
  • All of this is exposed to the assistant over a single remote endpoint
When to use it
Useful when an assistant should provision or query Supabase-compatible Postgres databases, branch them for experiments, and manage related auth, storage or email without a local database setup.
Requirements
A remote MCP endpoint at api.scribase.com over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. No local package or runtime is needed.
Before you install
The server can run SQL and manage projects, branches, auth, storage and email, so assistant actions may create, change or delete data and accounts. Access is granted through OAuth to your Scribase account; review the scopes granted and the provider's data handling before connecting.

Installation

In SourceWeft

  1. Open Scribase 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/com.scribase%2Fscribase/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": {
    "scribase": {
      "type": "http",
      "url": "https://api.scribase.com/mcp"
    }
  }
}

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. v1.0.0LatestOct 13, 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.