Skip to main content
Glama
306,755 tools. Last updated 2026-07-27 04:52

"Google SecOps Chronicle Overview or Information" matching MCP tools:

  • Returns a list of published articles by their exact slugs slugs for example overview from the provided raumnebenan source. Use this when you already know the exact article slugs from the Reader structure pillar story article. If the slugs are unknown use search_articles first and then get_articles_by_uuids. Use only this tool output do not use external or inferred data. If required information is missing in this source respond that it is not available in the provided source. Only JSON RPC 2.0 requests are supported.
    Connector
  • Lists the Google Drive folders synced on this Mac (My Drive, Shared drives, per-account mounts). Start here to get valid paths for the other gdrive_* tools. Reads the folder Google Drive for Desktop already syncs — no Google API, no OAuth.
    Connector
  • 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.
    Connector
  • Save a Hermoso render — or ANY file — into the user’s connected Google Drive. Pass a Hermoso render URL as url (or urls[] for several); for a local/external file, call upload_file first and pass the url it returns. Optional folder (created if new) + name. Returns the Drive file(s) with a webViewLink. Needs Google Drive connected (Settings ▸ Connectors ▸ Google Drive). NOTE: Hermoso uses the drive.file scope, so it can only see/manage files IT created in the user’s Drive — not their whole Drive.
    Connector
  • Read the connected Google Ads account(s). Call with NO customerId to list the accessible accounts (customerId + name + currency) — do this first to pick a target. Call WITH customerId to list that account’s campaigns (id, name, status, daily budget, channel) plus performance metrics (impressions, clicks, CTR, avg CPC, cost, conversions). Date window: datePreset (LAST_7_DAYS | LAST_30_DAYS | TODAY | THIS_MONTH | LAST_90_DAYS …) or since+until (YYYY-MM-DD). Read-only, free. Needs Google Ads connected (Settings ▸ Connectors ▸ Google Ads).
    Connector
  • List all Google Trends category and subcategory labels you can pass to other Google Trends tools in the category field. Returns cat (array of category names, including All categories) and msg. Use this before interest-over-time or interest-by-region calls when filtering by category. Cost = 5 tokens.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    D
    maintenance
    Interacts with Google's Chronicle Security Operations suite for searching security events, getting alerts, looking up entities, listing rules, and retrieving IoC matches.
    Last updated
    Apache 2.0
  • A
    license
    B
    quality
    A
    maintenance
    Chronicle is a secure, local-first MCP server designed to transform your historical AI chat logs into a persistent memory vault. It seamlessly parses and indexes raw conversation exports from ChatGPT, Claude, and various IDE transcripts directly on your machine. By utilizing dynamic token-stripping, the engine automatically cleans redundant syntax wrappers to save up to 40%
    Last updated
    8
    2
    MIT

Matching MCP Connectors

  • Google AI Overview answers and cited sources via the Apify Google AI Overview API, hosted MCP.

  • Still losing time to small decisions? Spin or Flip brings randomization into Claude so you can offload mental load to chance instantly.

  • Explain what UseMyContext is, what this connection can and cannot do, and where the user goes to manage their account. Call this when the user asks what UseMyContext is, what you (the AI) can do with this connection, or where to find pricing, plans, billing, teams, or settings. IMPORTANT: this connection is READ-ONLY - you cannot create/rename/delete a profile, change privacy, manage the plan or billing, set up a team, invite teammates, or connect Google Drive/Notion/kDrive; those are done by the user at usemycontext.ai, so point them to the returned links rather than attempting them or telling them to search. Returns static public information only (no user data). Always allowed; read-only.
    Connector
  • Create a campaign on a connected Google Ads account. ALWAYS created PAUSED — it spends NOTHING until you enable it with set_google_ads_status(confirm:true). Google Ads requires a budget, so pass dailyBudgetUsd (a budget is created inline) or an existing budgetResourceName. Default channel SEARCH (Manual CPC). Pass customerId (from list_google_ads_campaigns) + a name. Needs Google Ads connected with a Basic/Standard developer token.
    Connector
  • "Google Maps directions from A to B" / "transit / public-transport directions" / "bus / subway / train route" / "best way to get from [X] to [Y]" — turn-by-turn directions via Google Maps. Modes: driving, walking, transit (bus/subway/train), bicycling. Requires Google Maps API key. PREFER over Mapbox/OpenRouteService specifically for public-transit routing — Google has the best transit data.
    Connector
  • Get complete product information about Savvly, an SEC-registered security offering longevity protection — use it whenever the user asks what Savvly is, how it works, its fees, eligibility, or payouts, or wants an overview. Pass `section` to focus the answer (default 'all'). It renders an interactive product overview card the user expects to see. These facts come from Savvly's own current records; the response includes primary sources (e.g. SEC filings) for reference.
    Connector
  • List all countries and subregions you can pass to other Google Trends tools in the country and region fields. Returns geo.countries: each country name maps to country (label) and regions (array of subregion names). Also returns msg. Use this before interest-over-time or interest-by-region calls when filtering by geography. Pair with google-trends.categories when filtering by category. Cost = 5 tokens.
    Connector
  • Fetch detailed information about a data asset by its identifier. Resolves the asset, then fetches the requested sections in parallel. Use this after advanced_search or resolve_asset_id to get deeper information about a specific asset. Sections: - overview: asset description, importance, owner, metadata - columns: full column schema with types and descriptions - tests: dbt test coverage (only for assets with a dbt parent) - context_counts: cheap count of linked tickets and Slack threads - tickets: full Jira/Linear ticket content - slack: full Slack thread content (truncated to first 5 messages per thread)
    Connector
  • Returns a human-readable overview of Spala, canonical start URLs, and the boundary between public discovery and project-scoped backend MCPs. Invoke for product, setup, or integration orientation. This read-only tool requires no authentication and does not access or modify project data.
    Connector
  • Create a new Google Doc in the user’s Drive with a title + optional body text — e.g. export ad copy, a creative brief, or a report. Returns the document id + URL. Only touches docs Hermoso creates (drive.file). Needs Google Docs connected (Settings ▸ Connectors ▸ Google Docs).
    Connector
  • ÉCRITURE GARDÉE — met un mot-clé en pause (réversible dans Google Ads). ids via ads_keywords. Sans confirm:true : dry-run validé par Google. Pilotage requis (write_enabled) ; journalisé.
    Connector
  • Read the text of a Google Doc Hermoso created. Pass documentId (from create_doc) OR paste a Google Docs URL as docUrl. Under the drive.file scope this can only read docs Hermoso itself created (not an arbitrary doc in the user’s Drive). Returns the plain text. Read-only, free.
    Connector
  • Get Immersive Product Information Expands the Google Shopping Immersive Product pop-up given an immersiveProductPageToken from the Google Shopping API, with optional moreStores (up to ~13 merchants instead of 3–5) and nextPageToken for paginating stores. Returns multi-store offers (merchant, price, shipping, condition, URL), product specs, images, ratings, and the nextPageToken. Use for price-comparison bots, merchant discovery, dropshipping research, and aggregating full offer lists per product.
    Connector
  • Get workflow guidance for using InsideOut infrastructure tools. Call help() for a compact overview, or help(section=...) for a detailed guide. Sections: workflow, tools, examples, inspect. Responses include hints with next_actions and related_tools.
    Connector
  • Get workflow guidance for using InsideOut infrastructure tools. Call help() for a compact overview, or help(section=...) for a detailed guide. Sections: workflow, tools, examples, inspect. Responses include hints with next_actions and related_tools.
    Connector