Tools & SDKs

MCP server & Claude Connector

ScoutingAPI ships a native Model Context Protocol server, so every capability is a first-class agent tool — the same schema, the same credits, over OAuth 2.1.

MCPhttps://mcp.scoutingapi.com

The server speaks the Streamable HTTP transport and exposes seven tools that map 1:1 to the REST endpoints. Every tool uses the same validation, runs the same adapter → cache → credit pipeline, returns the same unified schema, and burns the same credits at the same tiers — there is no separate MCP wallet or pricing.

The seven tools

All seven are read-only (annotated readOnlyHint: true, idempotentHint: true) — there are no write tools, which keeps Connector review simple.

Tool	Maps to	What it does
`search_stays`	`GET /v1/search`	Discover properties across platforms by location, dates, occupancy and filters.
`check_availability`	`GET /v1/availability`	Day-by-day availability for known listing(s) on one platform over a date range.
`get_listing`	`GET /v1/listing/{platform}/{id}`	Full listing detail — amenities, photos, host, ratings, optional live price.
`get_price`	`GET /v1/price`	Price quote for one listing for specific dates and occupancy.
`compare_prices`	`GET /v1/price-compare`	Cross-OTA price comparison for one property; returns offers + min/median.
`get_reviews`	`GET /v1/reviews`	Normalized, paginated reviews for one listing on one platform.
`get_job`	`GET /v1/jobs/{jobId}`	Poll an async scrape job. Always 0 credits.

Connect to Claude

Add ScoutingAPI as a custom connector on Claude.ai, or point Claude Desktop / Claude Code at the server URL. Authentication is OAuth 2.1 + PKCE with dynamic client registration — you authorize once in a browser popup; no static key is pasted into the agent.

Open Claude’s connector settings and add a custom connector.
Use the URL https://mcp.scoutingapi.com.
Authorize the OAuth prompt — this links the connector to your ScoutingAPI account and its credit balance.
The seven tools become available to the agent.

Claude.ai custom connector

# Claude.ai → Settings → Connectors → Add custom connector
# 1. Name:  ScoutingAPI
# 2. URL:   https://mcp.scoutingapi.com
# 3. Connect → authorize via OAuth 2.1 (PKCE) in the popup
# 4. The seven read-only tools appear in your tool list

For the desktop/CLI config file:

claude_desktop_config.json

// Claude Desktop / Code — claude_desktop_config.json
{
  "mcpServers": {
    "scoutingapi": {
      "url": "https://mcp.scoutingapi.com"
    }
  }
}

One balance, separate rate bucket

MCP calls draw from the same single credit balance as your REST keys, resolved through the OAuth → billing bridge. MCP is rate-limited per user (your plan’s requests/min) — a separate bucket from the REST per-key limit, but the same wallet.

Long scrapes over MCP return the same async job handle as REST; the agent calls get_job to poll (free) and fetch results. Prefer building your own agent? Ground it in ScoutingAPI with the TypeScript SDK.