Google Jobs MCP Server

Created By
ChanMeng666a year ago
【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 parameters, and smart error handling.
Overview

What is Google Jobs MCP Server?

Google Jobs MCP Server is a Model Context Protocol (MCP) server implementation that provides Google Jobs search capabilities through SerpAPI integration, allowing users to search for job listings efficiently.

How to use Google Jobs MCP Server?

To use the server, install the necessary dependencies, configure your environment with a SERP API key, and start the server to begin searching for jobs.

Key features of Google Jobs MCP Server?

  • Multi-language support (English, Chinese, Japanese, Korean)
  • Flexible search options with various parameters (job title, location, employment type, etc.)
  • Smart error handling with helpful messages and suggestions
  • Rich job details including company benefits and application links
  • Pagination and sorting options for search results

Use cases of Google Jobs MCP Server?

  1. Job seekers looking for employment opportunities across different locations and job types.
  2. Developers integrating job search functionalities into their applications.
  3. Companies wanting to provide job search capabilities on their platforms.

FAQ from Google Jobs MCP Server?

  • How do I obtain a SERP API key?

Visit the SERP API website, create an account, and copy your API key from the dashboard.

  • Is there a free tier for using the SERP API?

Yes, new users get 100 free API calls per month.

  • What programming languages are supported?

The server supports multiple languages including English, Chinese, Japanese, and Korean.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ChanMeng666
Star
7
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago