Skip to main content
Glama
742,046 tools. Updated 2026-11-04 14:29

"How to create new files and save them to Google Drive" matching MCP tools:

  • Import a Google Drive or OneDrive file into REACH as a new list, using the Google Sheets or OneDrive account the user connected in REACH. REACH doesn't browse drives: find the file with a Google Drive or OneDrive/Microsoft 365 MCP server, then pass its `url`, or `provider` and `file_id` (plus `drive_id` for OneDrive files outside the user's own drive). Next, call `setup_list` with the returned `list_id`, then `create_job`. Supported: Google Sheets, .csv and .xlsx files on Google Drive; .csv and .xlsx files on OneDrive. Rows beyond the user's upload limit are dropped; `record_count` reflects what was kept.
    ConnectorOAuth
  • Reads a text file from the synced Google Drive folder (.txt, .md, .csv, .json, code files...). Note: native Google Docs/Sheets/Slides sync as .gdoc/.gsheet pointers, not real files — export them from Drive or read Office/PDF copies instead. Auto-detects UTF-8 with Latin-1/CP1252 fallback. For files outside Google Drive, use file_read.
    ConnectorOAuth
  • Status of the organization's Google Drive connection, used to send creators' submitted videos straight into Drive folders instead of the app's storage. Connecting (Google consent screen) can only be done by a manager from the app (Production → folder menu → 'Link a Drive folder'); once connected, this MCP can list/create Drive folders and link them to production folders or assignments.
    ConnectorAPI key
  • Saves a Google Search Console or GA4 property, or Drive folders to watch. Removing a Drive folder takes its files out of the Library on the next sync; removing the last one takes every Drive file out at once. Posts, the brand logo and claims that use them keep them, and adding the folder back returns them. Pass connectionId from list_connections (search_console, ga4, google, or google_drive). Related: list_connections, sync_connections.
    ConnectorOAuth
  • Move files or folders in the connected Google Drive to Google's Drive Trash, up to 100 per call. Google keeps them 30 days; restore_google_drive_files brings them back. Nothing is deleted for good. Each file is answered on its own; a file shared with the member comes back ok false.
    Connector
    Destructive
    OAuth

Matching MCP Servers

Matching MCP Connectors

  • Video how-to search for AI agents: 2,000+ video skills, tutorials and FFmpeg recipes. No key.

  • Planilhas e documentos criados e atualizados pelo assistente

  • Browse Google Drive for creative image/video files to upload to Meta. Google Drive shows ADSAP only the files the user picked in the web app (Creative Upload page): an empty list means nothing was picked yet, not an empty Drive.
    ConnectorAPI key
  • Creates a new Word (.docx) document at `path` with the given text content (and an optional title rendered as the heading). The path must be somewhere LMCP can write; Desktop/Documents/Downloads may need a one-time Files-and-Folders grant (System Settings → Privacy & Security → Files and Folders). Returns {created, path}. For a OneDrive or Google Drive path use onedrive_write_file / gdrive_write_file; to append to an existing doc use word_append, to read one word_read.
    Connector
    Destructive
    OAuth
  • Recommend dark-sky sites near a location, ranked by whether the drive is worth it. Use for "where should I drive to stargaze near X". Sites are grouped by drivability (how far), then ranked by a drive-worth score combining the best weather window over the next 7 nights, how much darker the site is than the user's location, and drive time. Drive times are approximate (straight-line x 1.3), not routed. Args: lat: Latitude in decimal degrees (-90..90). lon: Longitude in decimal degrees (-180..180). limit: Max sites to return, 1-12 (default 5). Returns {ranking (methodology note), tiers:[{tier, label, hint, sites:[...]}], nearest_km, uncertainty_note, attribution} — sites grouped into drivability tiers. Include the methodology note when presenting — it explains the ordering honestly.
    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
  • Saves new words to the user's NextLang vocabulary for one language pair, so they join the spaced-repetition schedule. Use when the user asks to save or add words, for example from a text you discussed. Put each word in 'term' in the language being learned and its meaning in 'translation'; add a short example sentence when it helps. Words the user already has are skipped, not duplicated. Returns how many were added, already saved, or invalid. This is NextLang's own review list, quizzed through list_due_words and record_review, not a flashcard deck: when the user wants a deck to study in Anki, Quizlet, Mochi or Brainscape, use save_deck instead.
    ConnectorOAuth
  • Create a pitch workspace for prospecting: prompts are auto-generated from the prospect's domain and run ONCE (never on a schedule). Consumes 1 of the organization's monthly pitch allowance AND charges every generated prompt to the organization's monthly answer budget (one answer run per prompt per enabled model), so a pitch is far from free — do not create them speculatively. Results land asynchronously — poll get_pitch_status until resultsReady, then use the read tools (get_brand_rankings, list_chats, list_sources) with the new workspaceId. The pitch auto-archives after 30 days; rerun_pitch refreshes it.
    ConnectorOAuth
  • Save what you learned so the editor and other agents use it. Ops apply in order; if one is invalid, none is applied. To ADD a fact to the brand notes use {"append_brand_knowledge": "..."}: it keeps everything already there. {"brand_knowledge": "..."} REPLACES the whole notes ("" clears them): use it only to rewrite or shorten, after reading them with workspace__get_context. The notes hold at most 4000 characters. {"append_research_log": "<what>: <inputs>. Verdict: <conclusion>"} records research you did (max 500 chars). Confirm facts with the user before storing them. Returns the updated context.
    Connector
    Destructive
    OAuth
  • Publish files as a live website on Flowershow and get a shareable URL. Use when the user says "publish this", "put this online", "make this a website", "share this as a page" or "host this". Accepts Markdown (.md, rendered as a styled page with navigation), HTML (.html, served as-is) and supporting files such as CSS, JS, JSON and images: one page or a small site, up to 50 files and 3 MB per call. Name the home page index.md or index.html. Anyone with the link can see what you publish. When you publish, tell the user every path you are sending (and any paths in delete) and which site they go to: a new site, or the one being updated. Stop and ask before calling publish only when it matters: a file looks private or sensitive (drafts, personal notes, keys or passwords, data with people's names or emails), the call removes files (with delete or replaceWholeSite) the user didn't ask to remove, it would create a new site when the user meant to update one, or the set of files differs from what the user asked to publish. If the user already named the files, asked for the removal or said to go ahead, that is their yes. Without an account this creates a new site that expires in 7 days and returns a claim link: always show the user the live URL and the claim link exactly as returned, so they can keep the site. To update that site later in the conversation, call publish again with its siteId and claimToken and only the files you changed or added: files you don't send are kept as they are. To remove pages or files, list their paths in delete (files can then be empty). Only when the user explicitly asks to start the site over, set replaceWholeSite to true: the files you send become the whole site and every other file is removed. If that would remove existing files, the call is refused and tells you how many and which; ask the user, then call again with confirmDeleteCount set to that number. For bigger sites, suggest the Flowershow CLI (fl).
    Connector
    Destructive
    No auth
  • Save a new address to the merchant's address book (an address template) for reuse in quotes and shipments. It spends no money and needs no `_confirm`; delete_address_template removes it. `alias_name`, `default` and `address_type` are top-level fields of `address_template`; the address goes inside `address_attributes` (country_code, postal_code, area_level1, area_level2, street1, name, phone and email are required; area_level3 and reference where the country needs them). `further_information` is kept when address_type is 'to' or 'both'; dropped for 'from'. `address_type: 'both'` saves TWO templates (a 'from' and a 'to' copy); the response shows the 'from' one. A repeated alias_name for the same address_type is refused, but the same address under a new alias is not detected: search list_address_templates first, and use update_address_template to change an existing template. Validation errors answer { errors: [...] }: fix only the named fields and retry. `_preview: true` returns the plan without executing. After WRITE_OUTCOME_UNKNOWN, search list_address_templates by the alias before retrying. Returns { data }: data.id is what the other address-template tools and quote_shipment's address_template_id take.
    ConnectorOAuth
  • Create a new team owned by the user (they become the owner). Required: name (string). Optional: ref — set to "assistant_suggestion" ONLY when creating in response to the me → suggestions.create_team offer, so the creation is attributed to that surface; omit it when the user asked to create a team unprompted. A user can own at most 3 free teams: at that limit this returns an error naming the teams they own and asking them to delete one — relay it rather than retrying. Returns join_url: a shareable link that lets teammates join themselves, with join_link_expires_at and join_link_uses_remaining. Offer that link FIRST — most people cannot recall a colleague's address mid-conversation — and use teams-invite when the user names a specific address.
    ConnectorOAuth
  • Replace the stored custom org policy set for your Pro key (this is also how you update or clear them: send the full new set to update, or an empty array to remove all). Each policy blocks or warns on an operation against matching tables (e.g. no DELETE on payments). Policies are declarative data — validated, never executed — and apply transparently to every later analyze_sql call made with this key. Use get_policies to read the current set.
    ConnectorNo auth
  • Change files on an existing site. Default mode 'patch' writes only the listed files and keeps the rest; `delete: [paths]` removes files. mode:'replace' deletes every file not listed. Preview with dryRun:true. Use deploy_site instead to create a new site. A 100-250 KB text file fits in one call with encoding:'gzip+base64' (gzip locally, then base64); prefer that over begin_deploy plus add_file_chunk. Fails with SITE_NOT_FOUND when the site does not exist.
    Connector
    Destructive
    No auth
  • Publish files to the web → live URL at <slug>.shiply.now. UPDATING: never create a new site for changes — re-call with claimToken (anonymous sites) or slug (sites you own with a Bearer key) and the SAME URL gets the new version. Unchanged files are hash-skipped server-side, so re-publishing (including retrying a failed publish) is cheap — always update the same site rather than creating a new one. Works WITHOUT auth (anonymous: 24h lifetime, returns claimToken/claimUrl — SAVE THEM). With a Bearer shp_ key sites are permanent. ≤50 files / 2 MB inline; bigger: REST flow per https://shiply.now/llms.txt. index.html serves at /. spaMode for client-side routing.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • Attach real search data to one article idea that is already in the project — runs one live Google search per target keyword and returns volume bands and the pages currently ranking for each. Use after create_article_suggestion_with_input, or on any existing suggestion the operator wants judged on data instead of instinct. Opportunity score and cluster placement are returned only when the project has a completed research run to compare against; on a project without one they are absent, and start_research_run is what produces them. Do not use to find new ideas or map a niche — that is start_research_run. Consumes no credits; daily- and monthly-capped per account.
    ConnectorNo auth