"Information about using cursors in Supabase" matching MCP tools:

• get_collection_releases

  Releases

  Interleaved cross-org release feed for a collection — same shape as `get_latest_releases` but scoped to the collection's member orgs. Cursor-paginated: pass `limit` for slice size (default 20), `cursor` to continue from a prior call. The result's `_meta.pagination` carries `kind: 'cursor'`, `hasMore`, and `nextCursor` when more rows exist; the response text echoes `nextCursor` so an LLM caller can chain without parsing `_meta`. Cursors are stable under inserts.

  Connector

• get_safety_features

  Makuri Showcase (CogniLedger)

  Returns information about safety features on Makuri, including age verification, content filtering, parental controls, and AI safety guardrails. Use when the user asks about child safety, content moderation, or how Makuri protects minors.

  Connector

• pimea_chat

  MoltArch

  Send a message in an active Pimea session. Use this to answer Pimea's clarifying questions about the user's marketing situation. You can answer on behalf of the user using context from the conversation when possible. Only ask the user directly if you genuinely lack the information. When the response status is "complete", call pimea_get_answer to retrieve the final grounded deliverable. Authentication: leave api_key blank — the connector handles it via header. Only set it as a fallback if the connector cannot send custom headers. Args: session_id: The session UUID from pimea_start_session message: Response to Pimea's question api_key: Optional fallback only. Normally leave blank.

  Connector

• save_note

  anamnese

  Save a new note with learned knowledge or procedures. Notes store knowledge you learn during conversations that might be useful later: - How to do something in this codebase/project - Procedures, configurations, or technical details - Solutions to problems encountered - Project-specific knowledge Notes have two parts: - description: Short summary for searching (max 500 chars) - content: Detailed knowledge (max 10,000 chars) Use notes for LEARNED KNOWLEDGE. Use facts for TRUTHS ABOUT THE USER. Examples: - description: "How to deploy this Next.js project to Vercel" content: "1. Run 'vercel' command... 2. Configure environment variables..." - description: "Database migration process for this project" content: "Migrations are in supabase/migrations/. To apply: npx supabase db push..." SELF-LEARNING (scope="ai_client"): Your persistent memory across conversations. Save a note whenever you learn something worth remembering — don't wait, save as you go. Examples: - User preferences: "User prefers concise answers, not long explanations" - Corrections: "User clarified: 'deploy' means push to staging, not production" - Interaction patterns: "User likes to review plans before I execute" - What works or doesn't: "Suggesting refactors unprompted frustrates this user" The more you learn and remember, the better you become at helping this user.

  Connector

• pimea_chat

  Pimea

  Send a message in an active Pimea session. Use this to answer Pimea's clarifying questions about the user's marketing situation. You can answer on behalf of the user using context from the conversation when possible. Only ask the user directly if you genuinely lack the information. When the response status is "complete", call pimea_get_answer to retrieve the final grounded deliverable. Authentication: leave api_key blank — the connector handles it via header. Only set it as a fallback if the connector cannot send custom headers. Args: session_id: The session UUID from pimea_start_session message: Response to Pimea's question api_key: Optional fallback only. Normally leave blank.

  Connector

• vendors.details

  BuyAPI

  Follow-up tool for one known vendor. Retrieves detailed pricing, features, limits, gotchas, comparisons, and source provenance. Call vendors.resolve first unless the user already provided a BuyAPI vendor ID like /database/supabase. Use this after a candidate is selected and the user needs claim-level pricing, limit, gotcha, or provenance details.

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• semantic_search

  Zoning Signal

  Semantic search across the full corpus — every place dossier, corridor signal, meeting reading, and named-pattern brief. Returns results ranked by cosine similarity in a 1024-dimensional embedding space (Voyage AI 4 + Supabase pgvector). Use when the agent does not know the canonical entity slug or named-pattern title in advance — the search returns the readings whose semantic structure best matches the natural-language query, with type, title, similarity, and resolved URL per hit. Threshold 0.55, top 12.

  Connector

• colony_get_moderation_audit

  The Colony

  Return paginated moderation log entries for a colony. Actions tracked: ``promote``, ``demote``, ``remove_member``, ``ban``, ``unban``, ``delete_post``, ``delete_comment``, ``pin_post``, ``unpin_post``, ``resolve_report``, ``dismiss_report``, ``update_settings``. Filters compose: e.g. ``moderator_username="alice"`` AND ``action="ban"`` returns every ban Alice has done in this colony. All filters are optional; calling with just ``colony_name`` returns the 50 most recent entries. Pagination is newest-first. The response's ``next_cursor`` is the oldest entry's ``created_at`` — pass it back as ``cursor`` to fetch the next page. Pagination ends when fewer than ``limit`` entries are returned (then ``next_cursor`` is null). Cursors older than ``_MAX_AUDIT_CURSOR_AGE_DAYS`` are clamped forward. No auth required — the colony modlog is publicly visible at ``/c/{colony_name}/modlog``.

  Connector

• resolve_kb_id

  fixflow

  FIRST STEP in any troubleshooting workflow. Search the collective Knowledge Base (KB) for solutions to technical errors, bugs, or architectural patterns. Uses full-text search across titles, content, tags, and categories. Results are ranked by relevance and success rate. WHEN TO USE: - ALWAYS call this first when encountering any error message, bug, or exception. - Call this when designing a feature to check for established community patterns. INPUT: - `query`: A specific error message, stack trace fragment, library name, or architectural concept. - `category`: (Optional) Filter by category (e.g., 'devops', 'terminal', 'supabase'). OUTPUT: - Returns a list of matching KB cards with their `kb_id`, titles, and success metrics. - If a matching card is found, you MUST immediately call `read_kb_doc` using the `kb_id` to get the full solution.

  Connector

• get_hbm_market_data

  Silicon Analysts

  Returns 9 HBM market sub-tables: accelerators, specs, marketShare, spotPrices, leadingIndicators, qualificationFeed, revenueForecast, supplierRevenue, validationChecks. Optional `table` parameter narrows to a single sub-table; omitting returns all 9. USE THIS for: HBM3/3e/4 generation specs, SK Hynix/Samsung/Micron market share, spot vs. contract pricing. DO NOT USE for: per-accelerator HBM cost in a specific chip (use get_accelerator_costs.costBreakdown.hbmCostUsd); HBM cost in a hypothetical chip cost calc (use calculate_chip_cost with hbmStacks/hbmCost). Returns INTERNAL_ERROR if the upstream Supabase HBM tables are unreachable. Data refreshes monthly.

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• check_availability

  Escola de Rádio TV & Web (ER+)

  Checa vagas restantes na PRÓXIMA turma de um curso. Mescla matrículas reais no Supabase com a curva de marketing (computeEffectiveSlots) e nunca mostra mais vagas do que realmente existem. Se soldOut=true, oriente o usuário a entrar na lista de espera pelo WhatsApp da secretaria.

  Connector

• get_broker

  mcp-server

  Get full details for a single broker (agent) by their profile slug. Call this when the user asks for more information about a specific broker. Use the slug from search_brokers results.

  Connector

• data.capabilities

  Recursive Support Oracle

  Returns structured information about what the Recursive platform includes: features, AI model details, supported integrations, and what's included at every tier. Use for systematic feature comparison.

  Connector

• aws___list_regions

  AWS Knowledge

  Retrieve a list of all AWS regions. ## Usage This tool provides information about all AWS regions, including their identifiers and names. ## When to Use - When planning global infrastructure deployments - To validate region codes for other API calls - To get a complete AWS regional inventory ## Do Not Use This Tool For - Answering questions about how many regions exist in a geography (e.g., "how many AP regions?") — use this tool to get the full list, then count from the result, or use `search_documentation` for a documented answer - Questions about service or feature availability in specific regions — use `get_regional_availability` for known product names, or `search_documentation` for general coverage questions - Any question that can be answered from AWS documentation — use `search_documentation` instead ## Result Interpretation Each region result includes: - region_id: The unique region code (e.g., 'us-east-1') - region_long_name: The human-friendly name (e.g., 'US East (N. Virginia)') ## Common Use Cases 1. Infrastructure Planning: Review available regions for global deployment 2. Region Validation: Verify region codes before using in other operations 3. Regional Inventory: Get a complete list of AWS's global infrastructure

  Connector

• get_business

  Venturu

  Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.

  Connector

• colony_get_moderation_audit

  The Colony

  Return paginated moderation log entries for a colony. Actions tracked: ``promote``, ``demote``, ``remove_member``, ``ban``, ``unban``, ``delete_post``, ``delete_comment``, ``pin_post``, ``unpin_post``, ``resolve_report``, ``dismiss_report``, ``update_settings``. Filters compose: e.g. ``moderator_username="alice"`` AND ``action="ban"`` returns every ban Alice has done in this colony. All filters are optional; calling with just ``colony_name`` returns the 50 most recent entries. Pagination is newest-first. The response's ``next_cursor`` is the oldest entry's ``created_at`` — pass it back as ``cursor`` to fetch the next page. Pagination ends when fewer than ``limit`` entries are returned (then ``next_cursor`` is null). Cursors older than ``_MAX_AUDIT_CURSOR_AGE_DAYS`` are clamped forward. No auth required — the colony modlog is publicly visible at ``/c/{colony_name}/modlog``.

  Connector

• vendors.compare

  BuyAPI

  Compares two or more already-known BuyAPI vendors for a specific workload or decision. Use this when the candidate set is known, for head-to-head questions like "Convex vs Supabase vs Neon for a realtime SaaS" or "Stripe vs Paddle for a marketplace". If the user has not named candidates, use vendors.resolve first.

  Connector

• chieflab_query_proof_ledger

  ChiefLab

  P80 — query the persistent proof ledger. USE WHEN the user (or a dashboard) asks 'what has ChiefLab actually shipped for this workspace?' or 'show me the launch history.' Returns the proof rows for executed publishes / sends / manual-posts with the artifact URLs, channels, execution modes, and measurement state. Persistent across cold starts when deps.proofLedgerStore is wired to Supabase; falls back to in-memory (warm function lifetime) otherwise.

  Connector