---
title: "Remote MCP server (streamable HTTP, JSON-RPC 2.0). Tools search, news, maps, scholar, webpage"
method: POST
path: "/v1/mcp"
---

# Remote MCP server (streamable HTTP, JSON-RPC 2.0). Tools search, news, maps, scholar, webpage

`POST /v1/mcp`

## Request

- Base URL: `https://api.serpkite.com`
- URL: `https://api.serpkite.com/v1/mcp`
- Auth: one of:
  - HTTP bearer
  - OAuth 2 (authorization code, authorization URL `https://app-api.serpkite.com/oauth/authorize`, token URL `https://app-api.serpkite.com/oauth/token`, scopes: `mcp`)

Authenticates with an API key (`Authorization: Bearer skt_live_…`) or an
OAuth 2.1 access token (`skt_oat_…`) issued by app-api.serpkite.com for
this resource (MCP authorization spec). Without a valid credential the
401 carries `WWW-Authenticate: Bearer resource_metadata="…/.well-known/oauth-protected-resource/v1/mcp", scope="mcp"`
(plus `error="invalid_token"` when a credential was rejected). OAuth
access tokens are only accepted here, not on the REST endpoints.

## Request body

- object

## Response `200`

JSON-RPC response

- object

## Other responses

- `202`: Notification accepted
- `401`: Missing, invalid, expired or revoked credential

---

[API](https://skmtc.dev/serpkite/apis/serpkite-serp-api.md) · [All operations](https://skmtc.dev/serpkite/apis/serpkite-serp-api/llms.txt) · [OpenAPI document](https://skmtc.dev/serpkite/apis/serpkite-serp-api/revisions/f2c6dd05cfc5?raw)