Skip to main content
Glama
685,920 tools. Updated 2026-10-23 04:09

"Connecting MCP to Google Sheets for Editing and Modifications" matching MCP tools:

  • Finish connecting a Google Antigravity account started with add_antigravity_start. `code` is the value of `?code=...` on the antigravity.google/oauth-callback page the user landed on; `state` is what add_antigravity_start returned. Returns {status, account_id, account_email, requires_project}. By default this also creates the GCP project in one step (`complete=True`) and adds `project_id`. Pass `complete=False` to defer and call `complete_antigravity_account(account_id)` later. If auto-onboarding fails the result keeps `requires_project: true` and carries `onboard_error`; retry with `complete_antigravity_account(account_id)`. Errors: "unknown state" (start again) or "google_api_error" (the code was rejected or already used; start again).
    ConnectorNo auth
  • Which export destinations this account has connected (Close, GoHighLevel, Google Sheets) and whether each is ready to receive leads. Check this BEFORE export_leads or create_automation with a CRM destination — those fail if the integration isn't connected, and Close additionally needs one manual export first to save its field mapping. File destinations (csv/xlsx/json) always work and need nothing connected.
    ConnectorNo auth
  • Get a download link for every response to a form, as a spreadsheet (CSV, which opens directly in Excel, Numbers and Google Sheets) or as JSON. Use this when someone wants the whole dataset in their own hands — "send me the responses", "export this", "can I get a spreadsheet". Returns a link, not the data: a few thousand answers do not belong in a conversation. For questions you can answer here — counts, totals, which option is winning — use get_response_stats, and for reading particular answers use list_responses. The link works for one hour and needs no login, so treat it as sensitive and give it only to the person who asked. Example: { form_id: "…", format: "csv" }
    ConnectorOAuth
  • Start connecting the user's Instagram professional account. Returns `connect_url`: give it to the user exactly as it is; they approve on Instagram, land on saypage.ai, and come back here. Then call get_account to see the account. This never asks for permission to publish posts: see get_instagram_publishing_link.
    ConnectorOAuth
  • Search the workspace by content across sheets, pages, dashboards, items, tasks, employees, teams, and jobs. Returns up to `limit` ranked hits with kind/id/name/snippet. Use when the user references something by name ("the Pipeline sheet", "Sara's onboarding", "the launch blog") and you need its id to pass to other tools. Item-level search (rows inside sheets) covers all column content. Use `parentSheetId` to restrict to a specific sheet. Archived items are never returned; read them with `sheet.read` and `archived: "only"`. Email addresses and phone numbers in names and snippets come back as `[redacted]`.
    ConnectorOAuth
  • Get full details of a specific expense report including all expenses, totals, and compliance status. Use only when the user explicitly asks to inspect an existing report's details. Without checkFreshness:true, returns the stored report only. When explicitly requested together with analysisRequested:true, freshness reads canonical Google Sheets sources with a 5-second bound; if full tax-year replay is unavailable, status is unknown, not current. Never call this as a preflight or follow-up to creating, sharing, or billing from a report; those tools already return the requested result and links.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Lists integrations (Google, Search Console, GA4, Drive, analytics, CRM, email, Social publishing, and the website CMS) with health, last sync and failed jobs. Social publishing is one integration covering every social account, so this does not show which LinkedIn, Instagram or other accounts are connected: call list_channels for that. For the website CMS, call get_website_cms. For google_drive, lastSyncSummary has the last finished sync's counts: created, updated, unchanged, failed, complete, and skipped by reason (shortcut, unsupported_type, too_large, trashed, folder_not_readable). nextAction is the one-line total. What the customer can change per reason: shortcut, move or copy the original files into the shared folder (Mark does not follow shortcuts); unsupported_type, download Sheets, Slides, or Forms as PDF into the folder; too_large, files over 400 MB are not imported; trashed, restore the file; folder_not_readable, share the folder with Mark and add its link. Connecting still happens in the Mark app — call get_connect_link for the in-app URL, then sync_connections. connectionId is the provider name used by sync_connections, update_connection_settings, disconnect_connection and get_connect_link. Related: list_channels, get_connect_link, sync_connections, get_website_cms.
    ConnectorOAuth
  • Kick off a FULL accessibility audit deliverable for a URL — a persistent, timestamped artifact, not an inline scan. Runs the server-side pipeline (axe + advanced checks + mobile viewports + annotated screenshots + optional agent spot-check) and produces a downloadable report and a formatted Excel workbook (Cover / Status / Barriers / ADA context sheets) stored durably. Returns immediately with an audit `id`; poll `get_audit` for progress and, when complete, download URLs. Use this when someone needs a durable artifact to attach as evidence of testing effort for a compliance officer or legal response — for iterating on code, use scan_page + verify_fix instead. Needs a free WebAbility account (sign in by connecting https://mcp.webability.io/mcp/auth, or run `webability login`). Set includeAgent:true to add the slower agentic manual-audit pass. To audit a local dev server, open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` with the printed secret as `tunnel_secret`; keep the tunnel open until get_audit reports complete (about 5 minutes) — the pipeline loads the page several times.
    ConnectorNo auth
  • Discover AgentMarketplace's capabilities, tools, auth methods, and scopes. Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate. No authentication required. Returns a catalog of available tools, resources, auth methods, and scopes.
    ConnectorNo auth
  • Publish a multi-scenario comparison into the signed-in user's Google Sheets — sim_compare's export, the counterpart of sim_publish for a single scenario. Runs every scenario on one shared seed (the same server-enforced sharing sim_compare uses, so differences are the scenarios and not the dice) and writes a comparison table plus a trajectory chart, rather than one scenario's own data tabs. Returns the sheet URL. Counts against the same daily publish quota as sim_publish, and costs 1 token per scenario from your account's compute bucket.
    Connector
    Destructive
    OAuth
  • Start (or restart) connecting the merchant's Google Merchant Center to Pollen. Returns an authUrl that the HUMAN must open in a browser to grant Google consent - an agent cannot click it. After they approve, call get_google_connect_status to see where the flow landed (it may pause on an account picker or Terms-of-Service acceptance; resume with pick_google_account / accept_google_terms). Once active, Pollen publishes the enriched catalog automatically.
    ConnectorOAuth
  • List where your signals are delivered — Slack channels, webhooks, Google Sheets, n8n, Clay and Notion — with each destination’s health and recent failure state. Connection settings (URLs, tokens) are never returned.
    ConnectorOAuth
  • Start here when connecting an agent: explains what WorkspaceAlberta does, the search-to-bid-review workflow, handoff fields, data boundaries and unsupported actions. No model or network call.
    ConnectorNo auth
  • Download one Drive file's raw bytes as base64 (binary-safe — images, PDFs, etc.). NOT for Google-native Docs/Sheets/Slides (no raw binary exists — use read_file_content with export_mime_type instead). Hard-capped at 5MB; larger files error rather than silently truncating. Needs the Drive CONTENT scope (drive.readonly). Pass `account` when more than one content-capable account is connected.
    ConnectorOAuth
  • Run a read-only query against one of this organisation's connected databases — PostgreSQL, MySQL, SQL Server, Redshift, Snowflake, Oracle, BigQuery or Google Sheets — in that connection's own SQL dialect, and return rows. One SELECT, WITH, EXPLAIN or SHOW statement; a statement that could change data is refused. It returns at most 500 rows and about 100 KB: a larger result comes back cut, with truncated: true and totalRows, so prefer a LIMIT or an aggregate. Where a question involves a business number (revenue, churn, active users…), fastero_get_definitions holds this organisation's own expression for it.
    ConnectorAPI key
  • Start connecting a Google Workspace or Microsoft 365 mailbox by OAuth (no password). Returns `authorizationUrl` — give it to the USER to open in their browser and sign in — and a `state`. Then poll check_oauth_connect with that `state` every few seconds until it is `connected` or `failed`. The link expires in 10 minutes.
    Connector
    Destructive
    OAuth
  • Begin connecting a Google ANTIGRAVITY account (used by the Claude/Gemini models via OmniRoute — not a Google Flow account). Returns `authorize_url` and `state`. The next step is on the USER's side: give them `next_step` wording and the URL, they sign in and press Accept in their browser and hand you the `code=...` value from the antigravity.google/oauth-callback page. Then call add_antigravity_submit(code, state) with the `state` returned here.
    ConnectorNo auth
  • Find outliers and anomalies in structured data — ideal as a second step after pulling records from Google Sheets, Airtable, Supabase, Notion databases, HubSpot, Financial APIs, GitHub, NPM, or any source that returns rows of JSON. Fully stateless: send known-good rows as training and suspect rows as test in ONE call. Returns per-row anomaly scores, confidence levels, and the top features explaining WHY each row was flagged. Typical workflow: (1) Pull data from another tool (e.g. Google Sheets, Supabase query, HubSpot deals). (2) Pass the first N rows as training (normal baseline). (3) Pass remaining or new rows as test. (4) Report which rows are anomalous and why. Works on JSON objects, numbers, text, arrays. No separate training step required. Examples: - Spreadsheet QA: Pull 500 sales rows from Sheets → train on first 400 → test last 100 → flag outlier entries - Financial screening: Get ratios for 50 stocks from a financial API → find anomalous ones - CRM hygiene: Pull HubSpot deals → flag deals with unusual discount/value patterns - Dependency audit: Get NPM package metrics → flag packages with anomalous quality scores - Commit review: Pull GitHub commit metadata → flag unusual commit patterns
    ConnectorNo auth
  • Find outliers and anomalies in structured data — ideal as a second step after pulling records from Google Sheets, Airtable, Supabase, Notion databases, HubSpot, Financial APIs, GitHub, NPM, or any source that returns rows of JSON. Fully stateless: send known-good rows as training and suspect rows as test in ONE call. Returns per-row anomaly scores, confidence levels, and the top features explaining WHY each row was flagged. Typical workflow: (1) Pull data from another tool (e.g. Google Sheets, Supabase query, HubSpot deals). (2) Pass the first N rows as training (normal baseline). (3) Pass remaining or new rows as test. (4) Report which rows are anomalous and why. Works on JSON objects, numbers, text, arrays. No separate training step required. Examples: - Spreadsheet QA: Pull 500 sales rows from Sheets → train on first 400 → test last 100 → flag outlier entries - Financial screening: Get ratios for 50 stocks from a financial API → find anomalous ones - CRM hygiene: Pull HubSpot deals → flag deals with unusual discount/value patterns - Dependency audit: Get NPM package metrics → flag packages with anomalous quality scores - Commit review: Pull GitHub commit metadata → flag unusual commit patterns
    ConnectorNo auth
  • List the character sheets in the FilmLab cast register (id, name, age, gender, project_name, prompt_prefix_en). Call this BEFORE lab_generate whenever a person must look the same across several images: pass the id you find here as `character_refs` instead of re-describing the person in every prompt. Optional `search` matches name or project name (substring, case-insensitive). It shows YOUR OWN characters plus the public catalog (sheets explicitly made public and bound to no project). Characters of other accounts' projects never appear — projects can be confidential. New characters are private. The register returns at most 50 sheets, newest first, and offers NO paging — 20 are shown here. `total` therefore counts at most 50: with more than 50 sheets it understates, and `search` is the only way to reach the older ones. Nobody there yet? Create a sheet with lab_create_character.
    ConnectorOAuth