DEV Community

James Collins
James Collins

Posted on

Introducing SerpApi's Claude Code Plugin

Last year, we released the SerpApi MCP Server to give AI agents structured access to live search data through the Model Context Protocol. MCP works well across a range of clients — Claude Desktop, VS Code, Cursor, and others — but it requires running a server process, either locally or via our hosted endpoint.

For developers who work primarily inside Claude Code, Anthropic's agentic coding tool, there is now a lighter option. Today, we are releasing an open-source Claude Code plugin that gives Claude native access to 100+ search engines through the SerpApi REST API. No server to run, no SDK to install — just a plugin that teaches Claude how to search.

What Is a Claude Code Plugin?

Claude Code plugins are packages that extend what Claude can do inside its coding environment. A plugin can include skills — markdown instruction files that tell Claude how to use a specific tool or API — along with configuration for tool access and parameter schemas.

When a skill is relevant to what you are asking, Claude loads it automatically. The skill tells Claude which tools it can use, how to construct requests, and how to interpret results. In our case, the skill teaches Claude to call the SerpApi REST API directly using curl, pick the right search engine based on your intent, and summarize the results.

This is different from MCP. With MCP, the AI client communicates with a running server that wraps the API. With a Claude Code plugin, there is no intermediary — Claude reads the skill, understands the API, and calls it directly. Both approaches give you the same search data; they just differ in how the connection is made.

Key Features

  • Single skill, all engines. One skill — serpapi:search — covers every engine SerpApi supports. Claude selects the right one based on what you ask. Web search, shopping, maps, news, scholar, flights, jobs, finance — all through one interface.

  • Schema-driven accuracy. The plugin ships 107 JSON parameter schemas, one per engine. When Claude needs to construct a search for a specific engine, it reads the relevant schema to get the exact parameters, types, and options. No guessing.

  • Auto-invocation. You do not need to remember slash commands. Claude detects search-related requests and loads the skill automatically. You can also invoke it explicitly with /serpapi:search if you prefer.

  • Cost-aware defaults. The plugin defaults to Google Light for general web searches — it is faster and cheaper than the full Google endpoint. Claude also confirms before making API calls, since each non-cached call costs one search credit.

  • Always up to date. Engine schemas are regenerated weekly by CI and committed automatically, so the plugin stays in sync as SerpApi adds new engines or parameters.

  • Open source. The full plugin is available on GitHub. Contributions are welcome.

Getting Started

1. Get an API key

Sign up at serpapi.com — the free tier includes 250 searches per month, no credit card required. Then set your key as an environment variable:

export  SERPAPI_API_KEY="your_key_here"
Enter fullscreen mode Exit fullscreen mode

2. Install the plugin

Register the marketplace catalog and install:

/plugin marketplace add serpapi/serpapi-claude-plugin
/plugin install serpapi@serpapi-plugins
Enter fullscreen mode Exit fullscreen mode

Or, if you prefer to work from source:

git  clone  https://github.com/serpapi/serpapi-claude-plugin.git
claude  --plugin-dir  /path/to/serpapi-claude-plugin
Enter fullscreen mode Exit fullscreen mode

3. Search

Once installed, just ask Claude what you need in natural language:

Search for the best noise-cancelling headphones under $300

Find recent academic papers on retrieval-augmented generation

Compare prices for a PS5 on Amazon, Walmart, and eBay

Look up flights from SFO to Tokyo next month

Claude will pick the appropriate engine, construct the API call, execute it, and summarize the results — all without leaving your coding environment.

How It Works

Under the hood, the plugin is a single skill file backed by a directory of engine schemas. When Claude receives a search-related request, it:

  1. Loads the skill, which contains an engine selection table mapping intents to engines (e.g., "academic papers" → Google Scholar, "local restaurants" → Google Maps, "product prices" → Amazon).
  2. Reads the engine schema for the selected engine to determine the correct query parameter name and any engine-specific options.
  3. Constructs and executes the API call to the SerpApi REST endpoint.
  4. Summarizes the results in a readable format with source links.

Every SerpApi engine follows the same REST pattern — https://serpapi.com/search.json?engine=ENGINE&... — so the skill teaches one pattern and parameterizes it across all engines. Claude can also chain multiple engines together for tasks like cross-platform price comparisons or multi-source research.

Supported Engines

The plugin covers the full range of SerpApi's search engine APIs:

Category Engines
Web Search Google, Google Light, Bing, DuckDuckGo, Yahoo, Yandex, Baidu, Naver
AI Search Google AI Mode, Google AI Overview, Bing Copilot, Brave AI Mode
Shopping Amazon, Walmart, eBay, Google Shopping, Home Depot
Local / Maps Google Maps, Google Local, Yelp, TripAdvisor, OpenTable
Research Google Scholar, Google Patents, Google Trends
News Google News, Bing News, DuckDuckGo News, Baidu News
Media Google Images, Google Videos, YouTube, Google Lens
Travel Google Flights, Google Hotels, Google Travel Explore
Jobs Google Jobs
Finance Google Finance
Apps Google Play, Apple App Store

MCP or Plugin — Which Should You Use?

If you are already using our MCP server, you do not need to switch. MCP is the right choice when you work across multiple AI clients — Claude Desktop, VS Code Copilot, Cursor, or custom agents — since it provides a single server that any MCP-compatible client can connect to.

The Claude Code plugin is a better fit if Claude Code is your primary environment and you want a simpler setup. There is no server process to manage, no Docker container to run, and no port to configure. You install the plugin and it works.

Both options return the same structured JSON from the same SerpApi endpoints. They cover the same engines and support the same parameters. Choose the one that fits your workflow.

What's Next

The plugin is open source and available now at github.com/serpapi/serpapi-claude-plugin. We are continuing to expand our AI integrations to make sure developers can access live search data wherever they work — whether that is through MCP, Claude Code plugins, or the REST API directly.

If you run into issues or have ideas for improvement, open an issue or pull request on the repository. And if you haven't tried SerpApi yet, create a free account to get started with 250 searches per month.

Top comments (0)