← All integrations

SearchAPI MCP server

5 operations0 webhooks

Read SearchAPI account usage and locations, run a search, and read a cached search.

Try SearchAPI with your agent

Connect SearchAPI, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in SearchAPI on my account, then run one read-only example and show me the result.

Runs once, when you ask

SearchAPI tools and triggers

Tools are what your agent can do in SearchAPI through Corsair's MCP server. Triggers are the SearchAPI events a routine can start from.

Searches

  • GetRead-only

    Read a cached search by id. Result rows are not stored.

    searches.get

  • HtmlRead-only

    Read cached search HTML by id. The HTML is not stored.

    searches.html

  • RunRead-only

    Run a search on any SearchAPI engine (google, google_news, bing, youtube, amazon_search, ...) with location, language, page and time filters. Returns organic results and every other section (answer box, AI overview, knowledge graph, news, local results). Uses one search credit. Results are not stored.

    searches.run

Account

  • GetRead-only

    Read account usage and the hourly limit.

    account.get

Locations

  • ListRead-only

    Look up Google locations by name.

    locations.list

Connect SearchAPI to Claude, ChatGPT or Cursor

  1. 1

    Connect SearchAPI in Corsair

    Add your SearchAPI API key once in Corsair. Corsair stores the credential encrypted and makes the SearchAPI API calls for your agent, so it never goes into a prompt or a config file. Connect SearchAPI

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs SearchAPI. On a ChatGPT personal plan, connect SearchAPI here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. Every SearchAPI operation only reads data, so it runs right away in every mode.

FAQ

Install corsair and @corsair-dev/searchapi, add the SearchAPI plugin, and connect with an API key. Then call methods like corsair.searchapi.api.account.get() from your app. Corsair syncs data per tenant.

Yes. SearchAPI requires an API key from your SearchAPI account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit SearchAPI, GitHub, Notion, Stripe, and the rest. Trigger SearchAPI from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for read SearchAPI account usage and locations, run a search, and read a cached search. Common builds include sync jobs, admin tooling, and agents that call SearchAPI APIs from your backend. Local DB entities let you query synced SearchAPI records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per SearchAPI API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/searchapi in the open repo. When SearchAPI ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your SearchAPI data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store SearchAPI data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put SearchAPI on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every SearchAPI operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.