Docs

MCP Server

Connect AI assistants and coding tools to ApiDatasets through a guarded Model Context Protocol endpoint.

Best launch path

Use the hosted Streamable HTTP MCP endpoint for tools that support remote MCP. For clients that only support local stdio servers, use the optional stdio bridge script.

MCP endpoint: https://apidatasets.com/mcp
Manifest: https://apidatasets.com/mcp.json
Well-known: https://apidatasets.com/.well-known/mcp.json
Stdio bridge: https://apidatasets.com/mcp/stdio.py

HTTP client config

Remote MCP support varies by client. For clients that support HTTP MCP servers with custom headers, use this shape and put your key in the Authorization header.

{
  "mcpServers": {
    "apidatasets": {
      "type": "http",
      "url": "https://apidatasets.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Stdio bridge config

Some clients still expect stdio. Download and inspect the bridge script, then reference it from the local MCP config. The bridge forwards standard MCP JSON-RPC messages to the hosted endpoint.

curl https://apidatasets.com/mcp/stdio.py -o apidatasets_mcp.py
less apidatasets_mcp.py

{
  "mcpServers": {
    "apidatasets": {
      "command": "python3",
      "args": ["/absolute/path/apidatasets_mcp.py"],
      "env": {
        "APIDATASETS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Demo mode

If no API key is sent, MCP tools only accept allowlisted sample values. This lets users try Geo, Tax, Flight, Company, and Jobs tools without turning the MCP endpoint into an open scraper.

geo_zip_lookup({"zip_code": "30301"})
flight_route_best_times({"route": "ATL-LGA"})
company_ticker({"ticker": "NVDA"})
jobs_salary_signals({"title": "cloud engineer"})

Production mode

When an API key is present, MCP calls are authenticated, rate limited, metered, and logged against the underlying dataset endpoint.

Authorization: Bearer YOUR_API_KEY
X-API-Key: YOUR_API_KEY

Supported MCP features

The server exposes read-only tools, resources for catalog/docs context, and prompts for common dataset workflows.

tools/list
tools/call
resources/list
resources/read
resources/templates/list
prompts/list
prompts/get
ping
logging/setLevel

Available tools

Dataset tools are read-only and return structured content plus text content for client compatibility.

geo_zip_lookup
geo_enrich
geo_city_search
geo_county_lookup
geo_timezone
tax_federal_brackets
tax_standard_deduction
tax_mileage_rates
tax_retirement_limits
tax_deadlines
tax_state_brackets
flight_reliability
flight_airport_delay_profile
flight_route_best_times
flight_airline_reliability
flight_cancellation_risk
company_domain
company_search
company_ticker
company_nonprofit_ein
company_nonprofit_search
company_classify
jobs_skill_trends
jobs_role_skills
jobs_remote_trends
jobs_companies_hiring
jobs_salary_signals

Security posture

The MCP endpoint validates Origin headers, keeps all tools read-only, applies demo guardrails, supports protocol-version headers, and avoids exposing raw ingestion source URLs in MCP results.

Demo: allowlisted + rate limited + unmetered
Production: API key + rate limit + monthly usage + request logs
Resources/prompts: public docs and catalog context only