Skip to main content
The Hrizn MCP is a hosted Model Context Protocol server that gives AI agents live, site-scoped dealership data through your Public API key.
Hrizn MCP ≠ Mintlify docs MCP. Mintlify’s free docs MCP helps agents read API documentation. Hrizn MCP lets agents call tools against this dealership’s live data (inventory, dealer DNA, citable content).

Endpoint

Transport: Streamable HTTP in stateless JSON mode. Authenticate every request with your dealership hzk_ key.

Required scopes

Create a key in Dealership Manager → API & MCP with the MCP (Read) preset for read tools, MCP (Read + Create) for content generation, or grant: For OEM Compliance Checking on pasted copy or Hrizn articles, grant compliance:write (included in MCP (Read + Create)). Freeform checks also require the dealership’s Compliance Checking plan feature (Pro+ / add-on). Lead with HIGH severity issues and suggested_replacement, apply selected fixes, then re-check. Automotive heuristics only — not legal advice. For Hrizn Market Maker tools (local listings, days supply, competitive set, pricing, VIN appraisal helpers), also grant market_data:read — use the MCP (Read + Market) preset. Those tools require an Unlimited plan (or an explicit Unlimited feature override). Without Unlimited, Market Maker tools return a clear upgrade error and never call the live data provider. Market segment tools use vehicle_type (new, used, or certified). For Hrizn Social Hub post and review-reply tools, grant social:write and reviews:write — use the MCP (Read + Social) preset. Those tools require an Unlimited plan (or an explicit Unlimited feature override) when called from MCP. REST Social Management keys for direct Public API use are unchanged. If a network is missing or needs reconnect, tools return guidance to connect in Dealership Manager → Social Profiles (OAuth cannot run from MCP). Keys are site-scoped. Rate limits inherit the dealership Public API limits. Market endpoints are vendor-costly — keep filters tight.

Pagination

List tools (find_vehicles, list_content, find_content_to_cite, get_content_opportunities, find_ideaclouds, list_social_posts, find_reviews) return has_more and an opaque next_cursor. When has_more is true, call the same tool again with the same filters plus cursor: <next_cursor>. Tool responses are compact JSON (not pretty-printed) to reduce token use.

Write confirmation (dry_run)

Mutation tools (social create/update/delete/unpublish/retry, publish_review_reply, content create, IdeaCloud create_content) require an explicit confirm gate:
  1. Call with dry_run: true to validate and preview (no write).
  2. Show the preview to the user and get approval.
  3. Re-call with the same args plus user_confirmed: true and the returned preview_token to execute.
The signed token is short-lived and bound to the API key, tool, and exact payload. Changed, missing, expired, or forged tokens return an error and do not mutate.

Wait helpers and social composites

Async generation and human media upload often need polling. Prefer the bounded wait tools over tight multi-turn loops:
  • wait_for_media_session / wait_for_content / wait_for_ideacloud / wait_for_content_compliance / wait_for_social_post — default ~20s budget (hard max 24s). On timed_out: true, re-call with the same id to continue. For compliance status not_checked, call trigger_content_compliance first.
  • Social posting: prepare_social_post (presence + optional upload session) → user uploads → wait_for_media_sessionfinalize_social_post with dry_run, then user_confirmed + preview_token.

Discovery profiles

tools/list is automatically filtered to the scopes on the authenticated API key. You can further reduce tool-definition context by adding a profile to the MCP URL: A profile only narrows discovery; it never grants a missing scope. Plan-gated tools remain visible when their required scope is present so they can return upgrade guidance.

Connect a client

Hrizn MCP speaks remote Streamable HTTP. Pick a client and paste the matching config — shapes differ (url / httpUrl / serverUrl, JSON vs Codex TOML). Dealership Manager → API & MCP has a logo picker for Cursor, Claude, OpenAI Codex, Gemini CLI, VS Code, Windsurf, OpenCode, Continue, Cline, Zed, JetBrains, and Amazon Q / Kiro.

Cursor / Claude Code

.cursor/mcp.json (or Claude Code MCP settings):
Set HRIZN_API_KEY to your hzk_ key before launching the client.

Claude Desktop

Settings → Developer → Edit Config (paste the key; Desktop often lacks env interpolation):

OpenAI Codex (ChatGPT desktop / Codex IDE)

~/.codex/config.toml — Codex uses TOML, not JSON:
Set HRIZN_API_KEY in the environment. Or use http_headers with a literal hzk_ value for local testing.

Gemini CLI

~/.gemini/settings.json — Streamable HTTP uses httpUrl (not url):

Windsurf

~/.codeium/windsurf/mcp_config.json — remote servers use serverUrl:

OpenCode

opencode.json (project) or ~/.config/opencode/opencode.json:

VS Code / Copilot

.vscode/mcp.json:

Continue

.continue/config.yaml (streamable-http):

Cline / JetBrains AI

Same mcpServers + url + headers shape as Cursor (Cline: cline_mcp_settings.json; JetBrains: Settings → Tools → AI Assistant → MCP).

Amazon Q / Kiro

MCP settings (mcp.json):

Zed

settings.jsoncontext_servers:

Tool catalog

IdeaCloud text-first curation checklist

There is no research graph canvas in MCP. Agents should:
  1. Offer list_ideacloud_suggestions or accept a freeform keyword
  2. create_ideacloudwait_for_ideacloud until complete
  3. get_ideacloud_outline — narrate clusters (do not dump every question)
  4. apply_recommended_selection (or start empty)
  5. Drill with get_ideacloud_cluster only as needed; mutate via set_ideacloud_selection (max 15) and always re-show the numbered basket
  6. update_ideacloud_settings then create_content
Consumed suggestions disappear from both the in-app Create IdeaCloud dropdown and list_ideacloud_suggestions.
Catalog cascade tools never return JATO facts, MSRP, or provider refs. There is no bulk catalog export — always walk year → make → model → trim one level at a time.

Example agent questions

  • “Who are the sales managers at this store?”
  • “Summarize this dealership’s brand voice and DNA.”
  • “What used inventory is aged 60+ days?”
  • “Which units are missing a Hrizn AI description?”
  • “Show me the AI write-up for VIN …”
  • “What IdeaClouds do we have on Camry?”
  • “Top content opportunities this week?”
  • “Unanswered Google reviews under 3 stars?”
  • “Which published articles can I cite with a live URL?”
  • “Give me a lot health snapshot — aging and merchandising gaps.”
  • “Are my used RAV4s overpriced vs the local market?”
  • “What’s market days supply for new Camrys near us?”
  • “Which aged units should I cut price on first?”
  • “Create a model landing from an in-stock Camry — ask me inventory vs catalog first.”
  • “Build a catalog model landing for 2026 Honda Civic Sport after walking the YMMT lists.”
  • “Compare two vehicles — for each ask inventory VIN vs year/make/model/trim.”
  • “Schedule a Facebook post for Saturday at 10am local — confirm timezone from get_dealer_context.”
  • “Attach this photo to an Instagram post — open the upload link, drop the file, then post.”

Social Hub posting checklist (MCP)

  1. prepare_social_post — resolve healthy platforms; set needs_media=true when the user will upload files (reconnect via Dealership Manager → Social Profiles if needed)
  2. Draft copy (+ hashtags) and confirm schedule vs publish_now (IANA scheduled_timezone from suggested_timezone)
  3. Media: none, durable HTTPS media_items, or open upload_urlwait_for_media_session until ready. If a pending upload link is lost, call prepare_social_post with the same media_session_id to reissue it without creating an orphan session.
  4. finalize_social_post with dry_run=true, show the preview, then re-call with identical arguments plus user_confirmed=true and the returned preview_token (pass media_session_id when using the upload bridge)

Security

  • Treat API keys like passwords. They are shown once at creation.
  • Prefer the MCP (Read) preset (least privilege). Add MCP (Read + Market) only for Unlimited dealers that need Hrizn Market Maker. Add MCP (Read + Social) only for Unlimited dealers that need Social Hub post/reply tools.
  • New MCP keys need IdeaClouds, content intelligence, and social read scopes for the expanded tools; rotate older keys to pick them up.
  • Revoke unused keys from Dealership Manager → API & MCP → API Keys.
  • Hrizn MCP does not store your key; each tool call forwards it to the Public API.
  • Media upload links are capability URLs (site-scoped, ~20 min TTL). Do not forward them; after status ready the token is invalidated.

Troubleshooting

Last modified on July 26, 2026