INTEGRATION

Three surfaces.
One record store.

Every feed is served three ways from the same normalized store: an MCP connector for Claude and AI agents, a records API for your systems, and delivered feeds — email or webhook — on your cadence.

SURFACE 01 · MCP CONNECTOR

Connected to Claude in two clicks.

STEP 01

Subscribe, copy your feed URL

After checkout, your dashboard shows the connector URL for each feed you own.

getmcpdata.com/mcp/fire-safety ACTIVE [copy]
STEP 02

Add it as a connector in Claude

Claude → Settings → Connectors → "Add custom connector." Paste the URL. Same steps on web and desktop.

STEP 03

Sign in with Google

Use the Google account tied to your subscription — we match it to your billing record and unlock the feed. OAuth 2.0, no password shared, no API keys to rotate. If a subscription lapses, the tool politely declines until you're back.

STEP 04

Ask in plain English

The feed shows up as a tool. Current records back, in seconds.

› new sprinkler permits in Tampa this week 2026-06-25 401 E Jackson St Apex Fire 2026-06-24 1200 W Platt St Guardian + 4 more · updated 6 min ago
SURFACE 02 · RECORDS API
BEARER

For your own systems

Token-authenticated JSON over HTTPS. Filter by county, ZIP, event type, and date; every record carries its source id, timestamps, and attributes.

GET /api/v1/fire-safety/records?county=Miami-Dade&since=2026-06-01 Authorization: Bearer ••••••••
SURFACE 03 · DELIVERED FEEDS
PUSH

On your cadence

Daily or weekly deliveries of what's new in your territory — email digest or webhook to your CRM. Optional drafted outreach on each record.

START

Pick a feed. The rest is minutes.

Explore feed catalogTalk to MCP Data
AUTH — OAuth 2.0 · Google sign-in
ACCESS — subscription = access
KEYS — none to manage on MCP
SUPPORT — in every dashboard