CONNECT APP
Build with SerpApi
Web & App Development
- API key
MCP
Give your agent SerpApi tools
Every SerpApi action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's SerpApi account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "serpapi",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Scrape Search:
const result = await mcp.callTool({
name: "serpapi-scrape-search",
arguments: {
engine: "Engine",
q: "Query",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "serpapi",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Scrape Search:
result = await session.call_tool("serpapi-scrape-search", {
"engine": "Engine",
"q": "Query",
})API PROXY
Call the SerpApi API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the SerpApi API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://serpapi.com/account.json",
})
// Any allowed SerpApi endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://serpapi.com/account.json
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9zZXJwYXBpLmNvbS9hY2NvdW50Lmpzb24?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run SerpApi actions from your backend
Connect a user's SerpApi account once, then run Scrape Search on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "serpapi-scrape-search",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
serpapi: { authProvisionId: "apn_xxxxxxx" },
engine: "Engine",
q: "Query",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="serpapi-scrape-search",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"serpapi": {"authProvisionId": "apn_xxxxxxx"},
"engine": "Engine",
"q": "Query",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "serpapi-scrape-search",
"configured_props": {
"serpapi": { "authProvisionId": "apn_xxxxxxx" },
"engine": "Engine",
"q": "Query"
}
}'TOOLS
SerpApi actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
EVENTS
SerpApi triggers
Event sources your backend can deploy for users and receive through a webhook.
No SerpApi triggers are available yet.
MULTI-APP
Use SerpApi with other popular apps
Most products don't stop at one integration. Pair SerpApi with the other apps your users rely on, and ship use cases that span both.
- App slug
- serpapi
- Authentication
- API key
- Categories
- Web & App Development
- Actions
- 1
- Triggers
- 0
- API proxy
- Available