Google MCP Server

Google Jobs listings with direct apply links via the Apify Google Jobs Scraper, hosted MCP. That is what the google mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

The Google Jobs API searches Google Jobs and returns clean, structured JSON, one record per listing. Each job includes title, company, location, source platform, the full description, structured highlights (qualifications, responsibilities, benefits), parsed metadata (posting date, schedule type, benefits), and direct apply links across platforms (LinkedIn, Indeed, company site, and more). Supports location targeting, location-radius search, country and language filtering, and pagination.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 1 tool. What each one is for:

• Prerequisites — 1. Clone the repository bash git clone https://github.com/johnisanerd/Apify-Google-Jobs-Scraper.git cd Apify-Google-Jobs-Scraper

What it needs from you

Configuration is passed through the environment: APIFY_API_TOKEN, YOUR_APIFY_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.11 or higher - An Apify account and API key (get a free key here) 1. Clone the repository 2. Install dependencies with UV 3. Configure your API key 4. Run the example

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Google's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by johnisanerd; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.