pulsemcp verified Safe content atomic mcp-remote

Alibaba Cloud Supabase

Multi-component MCP server implementation by Aliyun that provides AI assistants with complete access to Supabase project management, database operations, and cloud infrastructure through both the Supabase Management API and Alibaba Cloud GPDB integration. The implementation includes three main packages: a core Supabase server with tools for project creation, database migrations, Edge Functions deployment, branching workflows, storage management, and debugging capabilities; a PostgREST server for direct database CRUD operations via REST API; and utility functions including a StreamTransport for in-memory client-server connections. Built with comprehensive feature toggles, project scoping options, and read-only modes, it serves developers building Supabase applications who need programmatic access to their infrastructure, teams managing multiple Supabase projects through conversational interfaces, and organizations requiring automated database operations with integrated Alibaba Cloud analytics capabilities for enhanced data processing workflows.

Cognium trust score

90%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/aliyun/alibabacloud-supabase-mcp-server
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Alibaba Cloud Supabase from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"