Skip to content

Default MCP Catalog — Data & Cloud

Object storage, managed databases (relational / analytical / document), and hosting platforms. Google Cloud entries route through Google OAuth; Microsoft entries through Azure AD tenants; the rest carry the vendor's own OAuth issuer URI. BigQuery carries the pipeline tag — it's the only entry on this page used as both a query target and a long-running ETL endpoint.

Entries (17)

Click any card to expand the full spec inline — transport (Streamable HTTP / STDIO), authentication shape (OAuth 2.1 / API key / Bearer / none), required environment variables, vendor URL or stdio command, and the upstream docs link.

Google Drive 🔐

Google Drive

storage · global · preview preview

List, read, and upload files in Google Drive, manage permissions, shared drives, and folder structure. Google Workspace MCP (Preview).

Vendor   Google · T1 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
OneDrive & SharePoint 🔐

storage · global ga

Browse and edit OneDrive personal files and SharePoint sites, lists, document libraries via Microsoft 365 Agent365. Requires MS_TENANT_ID.

Vendor   Microsoft · T1 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Cloudflare 🔐

Cloudflare

cloud · global ga

Cloudflare umbrella covering Workers, R2, KV, D1, Workers AI, Browser Rendering, Hyperdrive, Queues, Logs, and observability.

Vendor   Cloudflare · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Vercel 🔐

Vercel

cloud · global ga

Inspect and manage Vercel projects, deployments, domains, environment variables, and observability via OAuth.

Vendor   Vercel · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Netlify 🔐

Netlify

cloud · global ga

Manage Netlify sites, deploys, build hooks, edge functions, and form submissions via OAuth.

Vendor   Netlify · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Heroku 🔐

cloud · global ga

Inspect Heroku apps, dynos, releases, config vars, addons, and logs via OAuth.

Vendor   Heroku · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Render 🔐

Render

cloud · global ga

Manage Render web services, background workers, cron jobs, and deploys via OAuth.

Vendor   Render · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Google Cloud Run 🔐

Google Cloud Run

cloud · global ga

Deploy and manage Cloud Run services, revisions, traffic splits, and jobs. Uses Google OAuth with the cloud-platform scope.

Vendor   Google · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Google Cloud Storage 🔐

Google Cloud Storage

storage · global ga

Manage GCS buckets and objects — list, upload, download, IAM, lifecycle rules. Uses Google OAuth.

Vendor   Google · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
BigQuery 🔐

BigQuery

database · global · pipeline ga

Query datasets, manage tables and views, and run jobs in Google BigQuery. Google OAuth with the bigquery scope.

Vendor   Google · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Neon 🔐

Neon

database · global ga

Provision and query Neon serverless Postgres — branches, roles, schema migrations, query analysis. OAuth.

Vendor   Neon · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Supabase 🔐

Supabase

database · global ga

Manage Supabase projects end-to-end — Postgres queries, Auth users, Storage buckets, Edge Functions. OAuth.

Vendor   Supabase · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
PlanetScale 🔐

PlanetScale

database · global ga

Query PlanetScale MySQL databases, manage branches, deploy schema changes via OAuth.

Vendor   PlanetScale · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Google Cloud SQL 🔐

Google Cloud SQL

database · global ga

Administer Google Cloud SQL instances (MySQL, Postgres, SQL Server) — databases, users, backups, and queries.

Vendor   Google · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Google Cloud Spanner 🔐

Google Cloud Spanner

database · global ga

Query Google Cloud Spanner instances and databases — globally distributed, strong consistency, SQL.

Vendor   Google · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
Google Cloud Firestore 🔐

Google Cloud Firestore

database · global ga

Query and manage Firestore documents, collections, composite indexes, and security rules via Google OAuth.

Vendor   Google · T2 vendor

Auth        OAuth 2.1

Click for transport · auth · required env · description · docs
SQLite 🛠

SQLite

database · global · community ga

[macOS] Query a local SQLite database — SELECT, schema introspection, plus INSERT/UPDATE/DELETE when permitted. The activated form is pre-filled to run: uvx mcp-server-sqlite --db-path…

Vendor   modelcontextprotocol/servers-archived · T2 community

Auth        STDIO

Click for transport · auth · required env · description · docs

Workflow combinations

The 17 entries on this page span object storage, managed databases, and hosting platforms. They compose naturally as data-pipeline assemblies:

  • Analytics report → dashboard uploadBigQuery (run the query) + Google Cloud Storage (drop the CSV) + Cloudflare (purge the cache so the next dashboard hit is fresh).
  • Cross-cloud DB readSupabase (Postgres-flavoured) + Neon (serverless Postgres) + PlanetScale (Vitess-on-MySQL). Same SQL surface, three providers — useful for cost / latency comparisons.
  • Deploy + verifyVercel (deploy) + Netlify (alternative target for the same build) + Render (worker tier). Pick whichever matches the project, but keep all three active if you maintain mixed-host fleets.
  • Google-stack data flowGoogle Cloud Run (job) + Google Cloud SQL (transactional store) + BigQuery (warehouse) + Google Cloud Storage (artifacts). One OAuth issuer (accounts.google.com) covers all four.
  • OneDrive / SharePoint document ingestOneDrive & SharePoint + downstream Notion (Productivity page) for staging into a doc store.

Auth & secrets

Every remote entry uses OAuth 2.1. One stdio entry needs no env at all.

Connection family OAuth issuer Extra env
Google Drive / Cloud Run / Cloud Storage / Cloud SQL / Cloud Spanner / Cloud Firestore / BigQuery https://accounts.google.com (per-product scopes)
OneDrive & SharePoint https://login.microsoftonline.com/${MS_TENANT_ID}/v2.0 MS_TENANT_ID
Cloudflare Cloudflare OAuth
Vercel Vercel OAuth
Netlify Netlify OAuth
Heroku Heroku OAuth
Render Render OAuth
Neon Neon OAuth
Supabase Supabase OAuth
PlanetScale PlanetScale OAuth
SQLite (stdio) None Node.js 18+; pass the database file path as the first arg

Google Cloud entries each request a specific scope — bigquery.read for BigQuery, cloud-platform for Cloud Run, cloud-spanner.data for Spanner. Spring AI Playground stores the granted refresh token under ~/spring-ai-playground/mcp/oauth-tokens/ so you don't reauthorise on every restart.

Picking guide

If you need… Reach for
Hot OLAP / dataset queries BigQuery
Transactional Postgres, serverless Neon · Supabase
Transactional MySQL, sharded PlanetScale
Long-tail document DB Google Cloud Firestore
Cheap blob store Google Cloud Storage
Same store with versioning + ACLs OneDrive & SharePoke (MS_TENANT_ID required)
Edge / CDN Cloudflare
Static-first hosting Vercel · Netlify
Container-on-managed-runtime Google Cloud Run · Render · Heroku