Zenserp MCP server
12 operations0 webhooks
Search results API for Google, Bing, and Yandex SERP data, reverse image search, Google Shopping products, and Google Trends.
Try Zenserp with your agent
Connect Zenserp, 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 Zenserp on my account, then run one read-only example and show me the result.
Zenserp tools and triggers
Tools are what your agent can do in Zenserp through Corsair's MCP server. Triggers are the Zenserp events a routine can start from.
Search
- BingRead-only
Search Bing and return structured SERP data
search.bing
- GoogleRead-only
Search Google and return structured SERP data
search.google
- Reverse ImageRead-only
Run a Google reverse-image search for a public image URL
search.reverseImage
- YandexRead-only
Search Yandex and return structured SERP data
search.yandex
Account
- Get StatusRead-only
Return the remaining request quota for the API key
account.getStatus
Batches
- ListRead-only
List submitted Zenserp batches
batches.list
Shopping
- Get ProductRead-only
Retrieve Google Shopping product details
shopping.getProduct
Trends
- GetRead-only
Retrieve Google Trends data for one or more keywords
trends.get
Metadata
- List CountriesRead-only
List supported Google country parameters
metadata.listCountries
- List LanguagesRead-only
List supported Google interface languages
metadata.listLanguages
- List LocationsRead-only
List supported geolocation targets
metadata.listLocations
- List Search EnginesRead-only
List supported search-engine domains
metadata.listSearchEngines
Connect Zenserp to Claude, ChatGPT or Cursor
- 1
Connect Zenserp in Corsair
Add your Zenserp API key once in Corsair. Corsair stores the credential encrypted and makes the Zenserp API calls for your agent, so it never goes into a prompt or a config file. Connect Zenserp
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Zenserp. On a ChatGPT personal plan, connect Zenserp here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, 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
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 Zenserp operation only reads data, so it runs right away in every mode.
FAQ
Install corsair and @corsair-dev/zenserp, add the Zenserp plugin, and connect with an API key. Then call methods like corsair.zenserp.api.account.getStatus() from your app. Corsair keeps each tenant isolated.
Yes. Zenserp requires an API key from your Zenserp 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 Zenserp, GitHub, Notion, Stripe, and the rest. Trigger Zenserp from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for search results api for google, bing, and yandex serp data, reverse image search, google shopping products, and google trends. Common builds include sync jobs, admin tooling, and agents that call Zenserp APIs from your backend.
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 Zenserp 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/zenserp in the open repo. When Zenserp 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 Zenserp data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Zenserp 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 Zenserp on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every Zenserp operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.