Google Jobs MCP Server

【Every star you give feeds a hungry developer's motivation!⭐️】A Model Context Protocol (MCP) server implementation that provides Google Jobs search

Local serverstdioTypeScript

What is the Google Jobs MCP server?

【Every star you give feeds a hungry developer's motivation!⭐️】A Model Context Protocol (MCP) server implementation that provides Google Jobs search capabilities via SerpAPI integration. Features multi-language support, comprehensive search. That is what the google jobs mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 8 tools. What each one is for:

  • query — Search query string (required)
  • location — Job location (optional)
  • posted_age — Post date filter (optional)
  • employment_type — Job type filter (optional)
  • salary — Salary range filter (optional)
  • radius — Geographic search radius (optional)
  • page — Pagination number (optional)
  • sort_by — Sort order (optional)

Getting it running

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: SERP_API_KEY, OPENAI_API_KEY. 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.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Google Jobs's toolset — query, location, posted_age and 5 more — is a fair guide to whether it matches your workflow. It is maintained by ChanMeng666; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Google Jobs's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • 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.

Available tools

ToolWhat it does
querySearch query string (required)
locationJob location (optional)
posted_agePost date filter (optional)
employment_typeJob type filter (optional)
salarySalary range filter (optional)
radiusGeographic search radius (optional)
pagePagination number (optional)
sort_bySort order (optional)

How to install the Google Jobs MCP server

{
  "mcpServers": {
    "server-google-jobs": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "SERP_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SERP_API_KEYCredential the server authenticates with.Yes
OPENAI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Google Jobs to query.
  • Use Google Jobs to location.
  • Use Google Jobs to posted age.

Frequently asked questions

You need Node.js, the server installed via npm or Smithery, and a SERP API key (obtained from serpapi.com). New users get 100 free API calls.