Skip to main content
Glama
813,081 tools. Updated 2026-11-20 20:20

"Supabase Platform Overview" matching MCP tools:

  • Get reference documentation for the Orderly Public Info API — a zero-auth single endpoint (POST /v1/public/query) for market, account, and platform data selected by a `type` field. Covers 24 query types (marketSummary, accountState, orderbook, candles, topAddresses, whaleContext, etc.); `queryType` accepts exact, partial, or fuzzy names and returns params, response fields, example, weight, and freshness; `category` lists a group (queryType wins if both are supplied); omit both for the overview and rate-limit rules. Read-only bundled docs — it does not call the endpoint. Use instead of get_api_info for zero-auth public data; use get_api_info for authenticated trading, get_indexer_api_info for historical analytics, and get_strategy_vault_api_info for vault data.
    ConnectorNo auth
  • Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.
    ConnectorNo auth
  • Create a new ad group under a campaign. Every ad group belongs to one platform (body.platform, a platform id such as google-ads): only that platform receives it, its ads and its keywords. Leave it out on a campaign that runs on one platform; name it on a campaign that runs on several (400 AD_GROUP_PLATFORM_REQUIRED lists them). It is fixed once created — use copy_ad_group to run the same ads elsewhere. Returns the full updated/created object. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.
    ConnectorAPI key
  • Start a Brain document file upload (PDF, DOCX, TXT or Markdown, 10 MB max): returns a signed upload_url that the client PUTs the raw file to, with the returned content-type header, and an upload_id valid for 2 hours. Then call aidelly_complete_brain_document_upload with the upload_id. Works only for clients with direct network access to Supabase storage, such as Claude Code or a local CLI; the hosted server hides it from browser-sandboxed chat clients, which use aidelly_add_brain_document instead. Requires workspace settings permission. Retry-safe with the same idempotency_key.
    ConnectorNo auth
  • Use this when the user wants the numbers for their posts: "how are my clips doing", "which TikTok took off", "how many views did my Short get", "show my scheduled posts". Returns per post the platform, status, post URL, caption, clip title, the latest views, likes, comments, shares and saves the platform sent (null = the platform sends no such count) and views at 1 hour, 24 hours and 7 days. platform: tiktok, youtube, instagram, ... or all (default). status filters draft, scheduled, posted or failed (empty = all; status "draft" lists the post_id that update_draft and delete_draft take). limit 1-50, newest first. Covers posts RipClip published or planned. Not for: a recap of the week (weekly_report), platform against platform (compare_platforms), what is growing fast (whats_taking_off) or follower counts (get_account_stats). Free and read only.
    ConnectorNo auth
  • Creates a new Dreamlit workflow draft or updates an existing draft from an outcome-oriented natural-language prompt. Use after get_status; use get_workflow_and_preview_url first when editing an existing workflow, then describe the steps to change by what they do, not by step id. Each call continues the workflow's current chat; pass startNewChat to start fresh. Broadcasts that are scheduled, sent, or cancelled can't be edited; duplicate them in the Dreamlit web app instead. Existing Supabase Auth workflows can be edited except for the immutable trigger step; creating Supabase Auth workflows must happen through Supabase Auth email setup in the Dreamlit web app. Side effect: may create or modify a draft, but does not publish or install live triggers. Returns the workflow/draft result, action-required or handoff details when more input is needed, and relevant app URLs. For a broadcast or scheduled email to a group, when the project's segments or current moment haven't been answered yet, the draft is saved and the result is clarification_required (kind project_context): look the answers up, save them with update_project, then call again to adjust the draft. On success, changes lists each step the call added, updated (with the fields that changed), or removed, read from the saved draft, and warnings names any planned change that saved nothing; trust changes over assistantResponse, which is Dreamlit's plan in its own words. Do not use for publishing, direct database changes, or low-level graph edits.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • MCP server for interacting with the Supabase platform

  • Google AI Overview answers and their cited sources. Paid, on Apify's hosted MCP.

  • Add recipients to the API Platform (Email API / SMTP) suppression list so they are rejected on future API Platform sends. It does NOT stop Marketing Platform campaigns: to stop campaigns reaching an address, unsubscribe the contact (update_contact) or import it as suppressed in the panel. Scopes: global (default) blocks every API Platform send; marketing blocks only PROMOTIONAL Email API messages (metadata campaignType PROMOTIONAL), NOT Marketing Platform campaigns; transactional blocks only transactional (non-promotional) API Platform messages. The request is all-or-nothing: an invalid address rejects the whole batch. This blocks future mail to those addresses — confirm with the user first. Set dry_run: true to validate without changing anything.
    Connector
    Destructive
    API key
  • Use this when the user, or the agent building the app, wants to check an app they control for exposed files and leaked secret keys before launch. A deeper security scan than check_app_security, for an app the caller controls (for example one the agent itself is building). It looks for sensitive things left publicly reachable: an environment (.env) file, an exposed .git folder, a directory listing, or a published source map. It also reads the app's own public code (the home page and its scripts) for the Supabase project it uses and for secret keys shipped to the browser (a Supabase service role or secret key, a database password, a paid AI key). It never contacts the app's database, never writes, and never stores, logs or returns any key; it reports the exposed PATH or the KIND of key, never a file's contents or a secret value. Because it probes an app directly, each scan runs only after ownership is proven now: call it once to receive a one-time code and a check id, add the code to the app (a meta tag on the home page, or a line in /7it-verify.txt), then call again with the check id and the scan runs.
    ConnectorNo auth
  • CALL THIS FIRST, before any other tool. Orientation map of the whole Admin API: the platform-wide conventions you cannot see from a schema, and six task areas — each listing what users ask for, the literal first calls that serve those requests, and the cross-module traps that would otherwise send you to the wrong module. Module names are namespace segments and several of them lie about their contents, so routing by name alone fails. Pass 'area' for that area's modules (purpose, gotcha, recipes) and its FULL trap list — the overview carries only the first two traps per area.
    ConnectorOAuth
  • provider_playbook({"provider":"supabase","topic":"grants"}) Use before implementing a feature that touches a provider, when setup or integration rules are needed. Returns versioned setup guidance, gotchas, dated changes, integration seams, existing repo checks and planned live checks with official sources. Available packs: supabase. Pass topic to return matching items; for a specific error use search_guides, for dated changes use recent_provider_changes. Limits: guidance only; does not connect to providers, read your project, run checks or verify that a feature works.
    ConnectorNo auth
  • Discover where a list can go in an Ad Platform Export: the ad platforms REACH supports, whether the user has connected each one, and the ad accounts of connected platforms. Pass `platform` and `account_id` to also get that account's existing Ad Platform Audiences, which `export_list_to_ads` can add to with `audience_id`. Pass `list_id` to see whether that list can be exported to each platform, and why not: only a list with Online Audience output can be, each platform has a minimum record count, and an expired list (`list_expired`, past its `expires_at`) can't be exported at all, so the user needs a new list, for example by running the job again. An unconnected platform is listed with `connected: false`. Connecting happens only in the REACH web app, on the Integrations page; ask the user to do it there.
    ConnectorOAuth
  • Start an Ad Platform Export: push a list's Online Audience to the user's connected ad account as an Ad Platform Audience. Not billed. Find the platform, `account_id` and, to add to an existing Ad Platform Audience, its `audience_id` with `ads_export_options`. Pass `audience_name` to create a new Ad Platform Audience instead. The export runs in the background; check it with `ads_export_status` and the returned `history_id`. Only one export of a list to a platform runs at a time. When one is already running, no new export starts: `already_in_progress` is true and the response describes the running export, whose account and audience may differ from this request.
    Connector
    Destructive
    OAuth
  • Add recipients to the API Platform (Email API / SMTP) suppression list so they are rejected on future API Platform sends. It does NOT stop Marketing Platform campaigns: to stop campaigns reaching an address, unsubscribe the contact (update_contact) or import it as suppressed in the panel. Scopes: global (default) blocks every API Platform send; marketing blocks only PROMOTIONAL Email API messages (metadata campaignType PROMOTIONAL), NOT Marketing Platform campaigns; transactional blocks only transactional (non-promotional) API Platform messages. The request is all-or-nothing: an invalid address rejects the whole batch. This blocks future mail to those addresses — confirm with the user first. Set dry_run: true to validate without changing anything.
    Connector
    Destructive
    API key
  • The platform's own overview for one connected account, by `platform`. linkedin: a personal LinkedIn profile's aggregated post analytics (impressions, members reached, reactions, comments, reshares, followers) over an optional dateRange; a LinkedIn Page (organization account) is refused here, get_account_analytics and list_linkedin_live_posts cover a Page. youtube: channel statistics (subscribers, total views, video count) and the latest uploads with per-video stats; limit up to 50, default 15. bluesky: profile stats (followers, following, post count) and recent posts with per-post metrics; limit up to 50, default 20. pinterest: a 30-day account summary and recent pins with per-pin metrics. instagram, facebook, threads: the Meta-family overview; availability varies per account, so the response may be real metrics, {state: "permissions_required"} (platform permissions pending) or {state: "unavailable"} (the platform refused the fetch), and those states carry no numbers. dateRange (LinkedIn) and limit (YouTube, Bluesky) are refused on any other platform. An expired connection returns a reconnect error. For one account over any date range with a per-post table, on every platform, use get_account_analytics.
    ConnectorOAuth
  • Add or update a lead's social/profile link for a platform — upserts by platform, so re-adding the same platform (e.g. 'linkedin') overwrites its url/label instead of duplicating; this is also how you EDIT an existing entry. Stored in leads.social_urls, a jsonb array of {platform, url, label?} — use this tool rather than update_lead to change it, so one add can't clobber another entry already in the array. Required: lead_id, platform, url. Optional: label (free text, e.g. a headline or note). Returns the full updated social_urls array.
    ConnectorOAuth
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    ConnectorNo auth
  • Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.
    ConnectorNo auth
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    ConnectorNo auth
  • Returns the current skill cluster data for public jobs on the nü people website. Use this tool when the user wants an overview of which skills or technologies are currently in demand.
    ConnectorNo auth
  • Get full details for a specific developer tool, library or programming language by its slug (a library also answers to its package name, such as "pg" for node-postgres). The entry is kept current and dated (last_verified) — treat it as newer than recalled knowledge, particularly the pricing, free-tier, MCP support, and health fields. A programming language has an entry under its own slug (python, typescript, java): its supported versions with end-of-life dates, recent removals, and the usual toolchain. Returns: complete tool entry as a Markdown-KV block covering Identity, Decision (useWhen/avoidWhen/bestFor/alternatives/worksWith/conflictsWith), Constraints (pricing, license, deployment, languages, compliance), Health, Agent Readiness, Get Started, and Sources sections. Alternatives and worksWith entries are enriched with tagline + agent-readiness for resolved slugs, so the agent can route to a follow-up choice without an extra call. If the slug is not found, returns an error with similar-slug suggestions. Examples: - Postgres core engine: {slug: "postgresql"} - Stripe (single entry, no -cloud/-oss split): {slug: "stripe"} - Hosted Redis: {slug: "redis-cloud"} Self-hosted Redis: {slug: "redis-oss"} - Hosted Supabase: {slug: "supabase-cloud"} OSS Supabase: {slug: "supabase-oss"} - GitHub's MCP server: {slug: "github-mcp"} Edge cases: - 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: `{base}-cloud` for the managed lane, `{base}-oss` for the self-hosted lane (redis, supabase, mongodb, docker, elasticsearch, grafana, terraform, ...). Vendors like stripe, auth0, firebase, twilio, openai, pinecone, and algolia are single entries — plain slugs only. - Slugs derived from package names use hyphens where the name uses a dot (e.g., "nextjs" not "next.js"; "vuejs" not "vue.js"). - Slugs are case-sensitive lowercase. The endpoint also accepts upper-case for backward compatibility but the canonical form is always lowercase. Risk: read-only, closed-world, idempotent — no state change possible.
    ConnectorNo auth