otherapi_key

Autom

Autom is a service that delivers lightning-fast search engine results page (SERP) outcomes for Google, Bing, and Brave, offering developers rapid access to search data with minimal latency.

Verdict

Autom brings Google's location, language, and image search data into your Switchy workspace. @mention it to pull country lists, language codes, location metadata, or image URLs without leaving your conversation. Marketing teams use it to scope campaigns by geography, developers grab localization codes for i18n work, and content teams source images on the fly. It requires an API key from Autom's platform — setup takes under two minutes once you have credentials.

Common use cases

  • Scope ad campaigns by Google-supported countries
  • Pull language codes for app localization
  • Find location metadata for geo-targeted content
  • Source images for blog posts or social media
  • Validate country or language support before launch

Integration

Vendor
Autom
Category
other
Auth
API_KEY
Tools
4
Composio slug
autom

Tools

  • Google Countries

    Tool to list google-supported countries. use when you need to filter or suggest countries based on a search string.

  • Google Images

    Tool to fetch images from google search results. use when you need urls, titles, domains, and metadata for images matching a query.

  • Google Languages

    Tool to retrieve google-supported languages. use when you need a list of language codes for localization.

  • Google Locations

    Tool to retrieve google-supported locations. use when searching for locations by name. returns locations ordered by reach (most populous first).

Setup

Setup guide

  1. 11. Open your Switchy workspace and navigate to Settings > Integrations > Browse MCP Servers. 2. Search for Autom and click Connect. 3. You'll be prompted to paste an API key — get yours from the Autom dashboard under API Access. 4. Paste the key into Switchy and click Authorize. 5. Return to any Space and type '@Autom list countries matching canada' to confirm the connection works. 6. If you see results, the integration is live and ready to use across all Spaces in your workspace.

What teammates see: by default, memories from Autom are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List Campaign Countries

@Autom list all countries matching 'europe' so I can plan our Q2 ad spend by region.
Open in a Space →

Get Language Codes

@Autom show me the language codes for Spanish, French, and German so I can update our i18n config.
Open in a Space →

Find Location Metadata

@Autom search for locations matching 'san francisco' and return the top three by reach.
Open in a Space →

Source Blog Images

@Autom find images for 'remote work setup' and give me the top five URLs with titles and domains.
Open in a Space →

Validate Market Support

@Autom check if Google supports 'Vietnam' and 'Vietnamese' so we know if we can launch there next quarter.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Autom find images of sustainable office furniture for our new workspace design deck

Output

Found 10 image results for 'sustainable office furniture'. Top results include: a bamboo standing desk from EcoOffice.com (1200×800px), a recycled plastic chair collection from GreenWork (1920×1080px), and modular shelving from Sustain Furniture Co. (1600×900px). Each result includes the source domain, image dimensions, and direct URL. This illustrative example shows how the MCP returns structured metadata you can drop directly into design documents or presentation decks.

Notes

This example uses the Google Images tool to retrieve visual assets with metadata. The MCP returns URLs and dimensions but doesn't download files — you'll need to fetch images separately. Results depend on Google's current index and may vary by region. Useful for quick visual research without leaving your workspace.

Prompt

@Autom what languages should we support for our EU product launch? prioritize markets with high reach

Output

Google supports 135+ languages. For EU product launches, prioritize: English (en), German (de), French (fr), Spanish (es), Italian (it), and Polish (pl). These cover the largest populations and purchasing power in the region. Each language code follows ISO 639-1 standard, ready for i18n configuration. This illustrative response shows how the MCP helps you scope localization work by surfacing language codes with context about market reach.

Notes

This example demonstrates the Google Languages tool for localization planning. The MCP provides language codes but doesn't include demographic or economic data — you'll need to cross-reference market research. Helpful when scoping translation work or configuring multi-language products. No side effects; this is a read-only lookup.

Prompt

@Autom we're targeting ads in California — show me all google-supported locations matching 'san' so we can pick the right geo targets

Output

Found 8 locations matching 'san': San Jose, California (most populous), San Francisco, California, San Diego, California, San Bernardino, California, Santa Ana, California, Santa Clara, California, Santa Rosa, California, and San Mateo, California. Results are ordered by population reach. This illustrative example shows how the MCP helps you narrow geographic targeting by surfacing location names in priority order, ready to use in ad campaign setup.

Notes

This example uses the Google Locations tool to filter geographic targets for advertising or analytics. The MCP returns locations ordered by reach but doesn't include population counts or demographic breakdowns — you'll need to verify targeting scope in your ad platform. Useful for scoping campaigns without switching tools. Read-only; no account changes.

Use-case deep-dives

Localization planning for product launch

When Autom speeds up market research for international rollouts

A 6-person product team is scoping a European expansion and needs to validate which countries and languages to prioritize. Autom's Google Countries and Google Languages tools pull the full list of supported locales in under a minute, letting the team cross-reference against their analytics data without manually scraping Google Ads documentation. The Google Locations tool orders results by population reach, so you can quickly spot high-value metros. This works best when you're in the early research phase and need structured reference data fast. If you're already deep in a localization platform like Phrase or Crowdin, you probably don't need another API key. But for teams without a dedicated localization stack, Autom turns a two-hour research task into a five-minute Switchy query.

Content research for blog posts

When Autom's image search fits editorial workflows

A 3-person content team is drafting a blog post on sustainable packaging and needs royalty-free images with metadata for attribution. Autom's Google Images tool returns URLs, titles, and source domains in one call, so the team can preview options and check licensing in Switchy without opening 15 browser tabs. This is faster than manual Google Image searches when you're batching research for multiple posts. The trade-off: you still need to verify licensing on the source site, and if your team already uses Unsplash or Pexels APIs, those are purpose-built for editorial use. Autom wins when you're doing exploratory research across mixed sources and want structured metadata upfront. If you're publishing daily and need a vetted asset library, invest in a proper DAM instead.

Ad targeting setup for campaigns

When Autom bridges the gap before full ad platform access

A 2-person growth team is drafting a Google Ads campaign and needs to confirm which locations and languages are supported before requesting budget approval. Autom's Google Locations tool lets them search by city name and see population-ordered results, so they can prioritize high-reach metros without logging into Google Ads Manager. This is useful when the team doesn't yet have admin access to the ad account or is in the proposal stage. The limitation: Autom doesn't pull live ad performance data or bidding insights, so once the campaign is live, you'll switch to the Google Ads API or a tool like Supermetrics. Autom is the right call for pre-launch research when you need quick validation on targeting options, not ongoing campaign management.

Frequently asked

What does the Autom MCP do in Switchy?

The Autom MCP gives your AI agents access to Google's reference data — countries, languages, locations, and image search results. Your team can ask the AI to find images matching a query, suggest countries for a campaign, or pull location codes for ad targeting without leaving the conversation. It's useful for marketing ops, content research, and localization workflows where you need Google's canonical lists.

Do I need a Google account to use the Autom MCP?

No. Autom uses its own API key for authentication, not Google OAuth. You'll get the key from Autom's dashboard and paste it into Switchy's integration settings. This means you don't need admin access to a Google Workspace or Ads account — just an Autom subscription. The setup takes under two minutes.

Can the Autom MCP run Google Ads campaigns or pull analytics?

No. This MCP only accesses Google's public reference data — country lists, language codes, location names, and image search results. It can't create ads, pull performance metrics, or touch your Google Ads or Analytics accounts. If you need campaign management, use the Google Ads MCP or the official API directly.

Why use this instead of just Googling things myself?

The Autom MCP lets your AI pull structured data mid-conversation without you switching tabs. Instead of manually searching for "French-speaking countries" and pasting a list, the AI fetches it in real time and uses it to draft your brief or filter your audience. It's faster when you're building workflows that need Google's canonical reference data repeatedly.

Does connecting Autom count against my Switchy plan limits?

The connection itself doesn't count as a seat or workspace. However, every AI request that calls an Autom tool uses tokens from your plan's monthly budget. Image searches and location lookups are cheap — typically under 500 tokens per call — but they add up if your team runs dozens of queries daily. Monitor usage in your Switchy dashboard.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.