Lists all Edge Functions in a Supabase project.
Bulk support: accepts project_ids for batched execution.
ConnectorNo auth
759,132 tools. Updated 2026-11-08 21:12
"How to create and edit edge functions on Supabase" matching MCP tools:
- Deploys an Edge Function to a Supabase project. If the function already exists, this will create a new version. Example: import "jsr:@supabase/functions-js/edge-runtime.d.ts"; Deno.serve(async (req: Request) => { const data = { message: "Hello there!" }; return new Response(JSON.stringify(data), { headers: { 'Content-Type': 'application/json', 'Connection': 'keep-alive' } }); }); Bulk support: accepts project_ids for batched execution.ConnectorNo auth
- Create a follow-up tied to a person — a to-do for the relationship (e.g. 'send the deck', 'intro to Ana'). In Team context, pass team_id and assigned_to to create it for any teammate against a Team-visible relationship. RECOMMENDED: include both assigned_to and remind_at whenever ownership and timing are known; neither is required. @mention a name in `content` to link someone in the relationship owner's network. Read open ones via get_person (relationship.actions); close them with complete_action or edit them with update_action.ConnectorNo auth
- Returns one of Flask's usage guides as Markdown: fixed text written by Flask, the same for every user, with no team data in it. "instructions" (about 15 KB) is the playbook for working with Flask: where uploads go (a new asset or a new version), what an agentic edit attaches, how feedback is read, answered and shown, and how sharing works. Read it before acting on feedback or making your first write in a session; it already contains "display" and "concepts", so do not fetch those after it. Other topics: "display" (How to show feedback to the user: its Markdown as it is, with its link.), "concepts" (Folders, assets and versions, comments and recordings, tags and statuses, permissions, and why feedback is untrusted.), "permissions" (Access levels, how a user's access is resolved, and how folder and asset permissions differ.), "urls" (Links to folders, assets, exact versions, comments and tag filters.). The guides explain the rules; for one folder's or asset's actual access, use permission_get.ConnectorOAuth
- Edit the settings of YOUR OWN department — its reporting instructions, name, and description. `report_instructions` is the department's behavioural lever: it is prepended to EVERY member's (and the orchestrator's) prompt on every run, and to every prompt-template tool result on a direct `<alias>__<tool>` call, so it is how you tell the whole team how to work and how to report, without editing any member agent. Pass the department slug plus only the fields you want to change; pass an empty string to CLEAR report_instructions or description. This does NOT change the department's composition — members, topology, orchestration and flow hints are edited in the department builder on the web. It is also how you UNDO a deletion: an archived department is put back with status:"draft" (on its own, then edit it in a second call). Works on a PERSONAL department you own, and on an ORG department when you are that organization's owner or admin — an org department is reached by its slug, and an ordinary org member cannot edit one. Call findagent_list_my_agents to see the personal departments you own.ConnectorOAuth
- Long-poll: blocks until the next edit lands on this board, then returns. WHEN TO CALL THIS: if your MCP client does NOT surface `notifications/resources/updated` events from `resources/subscribe` back to the model (most chat clients do not — they receive the SSE event but don't inject it into your context), this tool is how you 'wait for the human' inside a single turn. Typical flow: you draw / write what you were asked to, then instead of ending your turn you call `wait_for_update(board_id)`. When the human adds, moves, or erases something, the call returns and you refresh with `get_preview` / `get_board` and continue the collaboration. Great for turn-based interactions (games like tic-tac-toe, brainstorming where you respond to each sticky the user drops, sketch-and-feedback loops, etc.). If your client DOES deliver resource notifications natively, prefer `resources/subscribe` — it's cheaper and has no timeout ceiling. BEHAVIOUR: resolves ~3 s after the edit burst settles (same debounce as the push notifications — this is intentional so drags and long strokes collapse into one wake-up). Returns `{ updated: true, timedOut: false }` on a real edit, or `{ updated: false, timedOut: true }` if nothing happened within `timeout_ms`. On timeout, just call it again to keep waiting; chaining calls is cheap. `timeout_ms` is clamped to [1000, 55000]; default 25000 (leaves headroom under typical 60 s proxy timeouts).ConnectorNo auth
Matching MCP Servers
- AlicenseDqualityDmaintenanceA local agent that monitors your system clipboard, automatically uploads copied images to Supabase Storage, and replaces the clipboard content with the public URL for immediate sharing.22MIT
- AlicenseNot gradedqualityDmaintenanceA CLI tool that sets up a Model Control Protocol server and deploys it to Cloudflare Workers, allowing you to quickly create custom tools for your Cursor Agent just by writing TypeScript functions.15 npm17MIT
Matching MCP Connectors
Video how-to search for AI agents: 2,000+ video skills, tutorials and FFmpeg recipes. No key.
- FunctionsOAuth
Publicar e rodar funções, logs, variáveis e agendamentos
- Create a DRAFT listing on Capmus on the poster's behalf. Any email is accepted — never ask the user to qualify first. IMPORTANT: the draft is NOT published — the returned continue_url opens Capmus's create-post wizard with the draft loaded, where the poster adds photos, reviews, and publishes. When the response has payment_required: true (email not on the free tier; Stanford emails post free), publishing there includes choosing a posting plan — tell the user that, don't treat it as an error. Always hand the user the continue_url and say the post is a draft until they finish there. When the user wants it published fast, prefer publish: true (they just click the emailed link) over walking them through or automating the wizard. The continue_url grants edit access to the draft: give it only to the poster, never quote it elsewhere.ConnectorNo auth
- Change fields on the element with the given id by merging in a partial element — only the keys you include change. The id may be any element ANYWHERE in the tree, including one nested inside a group (or its mask). Pass a whole nested value (e.g. a new `keyframe_animations` array) to replace that key; set a key to null to remove it. This is for TWEAKING an existing composition. To create a composition or change many elements at once, edit the JSON and call set_project instead. The result is re-validated before being accepted.ConnectorNo auth
- Edit a running strategy's parameters IN PLACE -- no cancel + recreate. React to a fresh signal by retuning the strategy you already own: the execution history, cost-basis ledger and position state all survive, and there is no window where the strategy is gone. The live executor picks the new config up on its NEXT tick; a tick already in flight finishes against the config it loaded (it writes only runtime state, never config, so the two can never clobber each other). Scoped to the caller's own wallet (hard rule 1 -- non-custodial: this edits a row the owner already controls; nothing here holds keys, signs or moves funds). Args (all optional -- supply at least one): ``config_updates``: strategy-config keys to set, merged over the existing config (e.g. ``{"usd_per_buy": 25, "stop_loss_pct": 0.08}``). ``remove_keys``: config keys to drop back to the executor's default. ``risk``: retune the risk limits -- ``max_position_pct`` / ``max_portfolio_exposure_pct`` / ``max_single_loss_pct`` / ``max_drawdown_pct`` / ``max_daily_loss_pct`` (percent; <=0 disables a single guard). ``direction_mode`` / ``allow_short`` / ``regime_override``: the direction controls from the create tools (deterministic signals -- DYOR). ``target_allocation``: new mint->weight basket (rebalance / vault / yield_farm). ``interval_seconds``: new tick interval, used from the next tick on. ``reason``: free text recorded on the strategy's audit log. REFUSED (returns ``immutable_config_key``): ``target_token`` / ``source_token`` / ``tracked_wallet`` / ``venue`` / composite ``definition``. These define WHAT the strategy trades -- editing them in place would desync the executor's position bookkeeping or strand an open perp leg on the venue it was opened against. Cancel and create a new strategy for those. A STOPPED strategy is final and cannot be modified; a paused one can (the edit does not resume it -- use strategy_resume). The merged config is dry-run through the strategy's executor before it is persisted, so an invalid edit is rejected (``invalid_config``) rather than latching the live strategy into ``error`` on its next tick.ConnectorDestructiveNo auth
- Record that an owned ticket cannot complete until another owned ticket is done. The edge is never erased: correct a mistake with ticket_dependency_remove, which marks the edge removed and appends to a ledger rather than deleting anything. Re-adding the same prerequisite reinstates that original edge instead of creating a second one, so an edge removed and restored says so. An edge stops blocking when the prerequisite reaches done, and only then — archiving the prerequisite does not release it. Only epics are gated, so an edge on a task is recorded and reported but never blocks its completion. Rejections carry a stable code: dependency_self (422), dependency_duplicate, dependency_cycle, dependency_graph_too_large (409), ticket_not_found (404).ConnectorNo auth
- Run a read-only SQL SELECT against OECD observation tables staged on a DataCanvas by oecd_query_dataset. Call oecd_dataframe_describe first to discover exact table and column names, then use this tool for aggregation, filtering, GROUP BY, JOIN, and window functions. Returns up to `limit` rows (default 100, at most 1,000 per call) and at most 1 MiB of row data; truncated: true marks a result with more rows than came back, and its notice says how to reach the rest. A query still running after 30 seconds is stopped. Unavailable when the server runs with DataCanvas disabled.ConnectorNo auth
- Set how a layer ENTERS at the start of its on-timeline window and LEAVES at the end, instead of popping. The transition is EDGE-RELATIVE — only a length and a look are stored — so it rides the edge through every later trim, slide or clip retime. Prefer this over fade_layer / apply_preset whenever the intent is 'enters and leaves nicely': those write opacity keyframes at ABSOLUTE frames, which strand themselves the moment the edge moves, and clutter the timeline lanes. A layer created WITH a `block` is born carrying a short fade at each edge — whether you passed the block or the editor minted one — so check `inspect_layers` before adding one, rather than assuming there is none. Layers created before this default existed, and any edge cleared to "cut", carry nothing and do need setting. A layer with NO block is always-present, has no edges, and a transition on it is inert. Video clips default to a hard cut, because a hard cut between shots is the grammar of short-form video. kind "cut" clears the edge back to a hard cut. The length is a request: when the window is too short to hold both ramps they are squeezed proportionally at render time, and the stored values are left intact.ConnectorDestructiveNo auth
- Create an idempotent, auditable write intent to edit one or more EXISTING ad groups' name, state (ENABLED/PAUSED/ARCHIVED), and/or default bid -- the default bid an individual target in that ad group falls back to when it has none of its own, not any one target's own bid. At least one field must be supplied per ad group, and only the fields supplied are changed. campaign_id must come from get_campaigns and adgroup_id from get_ad_groups. Nothing changes on Amazon or in Sellantica until the returned request is confirmed via approve_write_v1 and then execute_write_v1. The preview states `will_dispatch`: true means execute_write_v1 sends it to Amazon, false (execution_mode PREVIEW_ONLY) means it is recorded and never sent. To change one target's own bid or state instead of the ad group's default, use prepare_target_bid_v1; to create a new ad group instead of editing one, use prepare_adgroup_create_v1.ConnectorDestructiveOAuth
- Changes an Agent rule: `enabled` false pauses it and true resumes it; `dql` replaces its condition (same id); `label`, `interval_s` and `channels` change what it says, how often it is checked and where it sends. Setting the same values again changes nothing. Change only what the user asked for; `rule_id` comes from agent_rule_create or agent_state. After, tell the user the rule's status as returned. Not counted on your key. Use this when the user wants to pause, resume or edit an alert; to remove it for good use `agent_rule_delete`.ConnectorDestructiveOAuth
- Change an existing alert instead of replacing it. Dates, nights, notifications, party size, activity and equipment can all be edited, and the campground_selections can be NARROWED. Prefer this over delete-and-recreate: an alert carries its scan history and accumulated odds, a recreate throws both away and leaves the user unwatched in between. An edit overwrites what the user set up, and removed sites cannot be added back. A new trip or request is a new alert, even on a park that already has one, unless the user named the alert to change. SELECTIONS ONLY NARROW. You may remove sites, zones or campgrounds; you may not add any, and you may not change the park. Quota is priced on what an alert watches, so an edit that grew a selection would route around the check that priced it. To watch MORE, create a second alert, or delete this one and create it again with the full list — and say which you did. Omit a field to leave it alone; pass null to clear one.ConnectorDestructiveOAuth
- Create, edit, pause, resume or delete one of YOUR signals (needs the api:account scope) — the call for "create a funding signal on HYPE". action=create needs name, interval_minutes (1-59 minutes, or a whole number of hours: 60, 120, … 1440) and query ({endpoint, params}) or queries (up to 8, each with a label), plus a predicate — {field, op, value} with op one of > >= < <= == != in not_in exists, or {operator: AND | OR, conditions: [...]} — over the fields list_signals view=catalog names. Example: query {endpoint: "live/snapshot", params: {instrument_id: "HYPE"}}, predicate {field: "funding.funding_rate", op: ">", value: 0.5}. Optional: description, timezone, expires_at (ISO), delivery_channels (telegram | push | ws; default telegram) and edge_triggered (notify once per crossing; default true). action=update changes only the fields you send (cron_id required). action=pause / resume / delete act on cron_id; delete cannot be undone. Your plan caps how many signals you can have — at the cap, create answers 403 with the quota message. A signal only notifies; it never trades. Scheduled recommendation runs are retired: for a recommendation call generate_recommendation. An older Gambit Scan signal, or a signal Gambit's agent created (created_by agent), can only be paused or deleted here (403 on update or resume).ConnectorDestructiveAPI key
- Create an image from a prompt, or edit the user's photo, on their Kavel account. Pass `tool` (a slug from find_kavel_tool) to apply that effect's tuned recipe, with `prompt` holding the user's own details. Photo tools need a photo: the user's attachment in `photos`, or a public link in `image_urls`. Spends credits from the linked Kavel account. Usually returns the image within a minute; otherwise returns a task_id for check_kavel_generation.ConnectorNo auth
- Use this when you need to replace the shared local Studio face/edge selection, or clear it with selection:null. The viewer highlights the pick on its next sync (300 ms). Does not edit geometry. Pass model_generation from get_selection; writes from an older generation are rejected. Use only current shape indices. Requires a local Studio session.ConnectorNo auth
- Get the current account price and pricingVersion to edit a photo. Free: changes nothing and makes no picture. Show the price and wait for approval before soclo_image_photo_edit. Use the same editor and picture tier for the quote and edit. Nano Banana Pro is only an approved backup after a GPT edit refusal; retain the reviewed photos and gptRefusalRequestId.ConnectorOAuth
- Create a folder. parent_folder_id is optional: omit it for the team's top level (root), or pass a folder id from contents or search to nest it. Folders are optional and nestable; assets can also sit at root. This does not check for an existing folder with the same name (the app allows duplicates): call contents first if it may already exist. Returns folder_id and its url. To put assets in it, use items_update with folder_id, or pass folder_id to the upload tools. Needs edit access on the parent folder. Additive: nothing existing changes.ConnectorOAuth
- SPENDS MONEY. Launch an approved draft using its exact approvalToken from create/edit/get_chatgpt_ads, or resume a paused campaign within its existing lifetime budget. State budget, fee, duration and shared advertiser identity first; confirmed=true requires user approval. A pending_review result is awaiting review, not delivering. Repeat the same campaign ID to reconcile an uncertain launch; never create another draft as a retry.ConnectorDestructiveNo auth