Hrizn MCP works with your dealership’s data. A documentation MCP connection can only search these help pages.
Get started (OAuth)
- Sign in to Hrizn at app.hrizn.io.
- Open MCP in the left navigation (not Dealership Manager).
- Select at least one dealership rooftop and save your grant. OAuth without a saved grant returns
mcp_grant_required. - Copy the endpoint if you need it for a CLI, or follow the in-app walkthrough for Claude, Cursor, Codex/ChatGPT, or Gemini.
- Complete Hrizn sign-in when your AI client prompts, then ask a dealership-specific question to confirm tools are available.
Claude Desktop
- Complete the grant steps above on app.hrizn.io first.
- Follow the Claude walkthrough on the MCP page: Settings → Customize → Connectors → Add custom connector.
- Name it Hrizn, paste
https://mcp.app.hrizn.io/mcp, leave OAuth Client ID and Client Secret blank, then Connect and finish OAuth. - Under Tool permissions, keep write and delete tools on Needs approval unless you want them always allowed.
Claude Code
Install the public plugin, then authenticate:hzk_ API keys for new connections.
OpenAI ChatGPT / Codex
- Complete the grant steps on app.hrizn.io first.
- In Codex or ChatGPT desktop: Settings → Integrations → Plugins → MCPs → Add MCP server.
- Name it Hrizn, set type to Streamable HTTP, paste
https://mcp.app.hrizn.io/mcpexactly (no trailing slash — Codex derives its OAuth client identity from this URL), leave headers empty, Save. - Turn the server on and click Authenticate. Sign in with your Hrizn account.
next_steps, links, job); the interactive cards described below appear in ChatGPT, not in the Codex CLI.
Then run codex mcp login hrizn (or the Codex binary bundled in ChatGPT.app). If the browser lands on http://127.0.0.1:<port>/callback/... and the site cannot be reached, the desktop listener closed before Auth0 redirected — run codex mcp login hrizn again and finish OAuth in that session.
Cursor
Install from Cursor Directory (or the Hrizn Cursor plugin), complete OAuth when Cursor prompts, and keep your dealership grant saved on the MCP page. Walkthrough screens for Cursor in the Hrizn app are still being added. Until then, copy the Streamable HTTP with OAuth endpoint from the MCP page.Google Antigravity
Install the public Hrizn Antigravity plugin:~/.gemini/config/plugins/hrizn/ for all workspaces or .agents/plugins/hrizn/ for one workspace. The plugin uses this remote MCP configuration:
Other supported clients
VS Code, Windsurf, OpenCode, Continue, Cline, Zed, JetBrains, and Amazon Q/Kiro can connect to the same Streamable HTTP OAuth URL. Copyhttps://mcp.app.hrizn.io/mcp from the MCP page — we do not ship per-client config snippets.
The legacy API-key URL (
api.app.hrizn.io/v1/public/mcp) remains for existing integrations. New connections should use OAuth at mcp.app.hrizn.io.What you can do
Understand your dealership
- Summarize Dealer DNA, brand voice, staff, marketing priorities, and target geography
- Find dealership links and other account details
- Give outside agencies or approved partners useful dealership context
Work with inventory
- Search by make, model, year, price, mileage, age, color, trim, stock number, or VIN
- Review inventory mix, aging, and merchandising health
- Find vehicles missing Hrizn AI descriptions
- Retrieve details and descriptions for a specific vehicle
Work with search and traffic
- Review warehoused Search Console and GA4 (requires
analytics:readand Teams+ with API Access) - Notice movers with
get_search_snapshot/get_search_alerts, then diagnose a URL withget_page_performance(the only live inspect) - Package gaps with
get_create_brief, thencreate_ideacloudorcreate_content - Existing API keys must add
analytics:read; see the analytics guide
Plan and create content
- Find existing articles and published pages
- Review content opportunities and recommendations
- Explore IdeaCloud topics and questions
- Create IdeaClouds and turn selected ideas into content
- Build model landing pages, comparisons, and sales event pages
Check OEM compliance
- Review pasted ad, landing-page, or social copy
- Identify higher-risk language and suggested replacements
- Recheck copy after approved changes
- Check existing Hrizn content
- Accept fixes on stored articles — the suggested wording is saved into the article
- Dismiss findings with a reason, recorded in Hrizn so they stay resolved across re-checks
apply_content_compliance_fixes (issue_ids to fix, ignore_issue_ids to dismiss) — decisions persist with the article and appear in Composer. apply_compliance_fixes is the freeform variant for pasted copy: it returns revised text and stores nothing.
Compliance results are guidance based on automotive advertising rules. They are not legal advice.
Manage social activity
- Review connected social accounts, posts, and customer reviews
- Draft and publish review replies
- Create, schedule, update, or remove social posts
- Add media through a secure upload link
Use Hrizn Market Maker
- Review local listings and market days supply
- Compare inventory pricing with the local market
- Identify price-cut candidates and stocking opportunities
- Appraise vehicles and review comparable listings
- Explore vehicle options and packages
Tool catalog
Available tools depend on your saved grant, plan entitlements, and connected products. OAuth exposes the full entitled catalog; legacy API-key clients can narrow discovery with?profile=read|create|market|social|full.
For
find_vehicles, total_count remains the raw matching inventory aggregate
for backward compatibility. It can include malformed source rows omitted from
the returned vehicles. Use raw_total_count, invalid_row_count, and
total_count_includes_invalid_rows to interpret data quality without assuming
every counted source row is retrievable. invalid_row_count reports malformed
rows encountered during the bounded raw-page scan; it is not a whole-lot count
unless the scan reached the end.
IdeaCloud text-first curation checklist
Before creating content, review the IdeaCloud outline, cluster, and current selection. Apply a recommended or explicit selection only when the assistant presents the proposed change and you confirm it.Interactive cards and client support
Some results come with an interactive card (MCP Apps): inventory cards with an in-place market analysis, pricing tables, lot-health and price-analysis insights, the dealership briefing, content lists, social posts and reviews, IdeaCloud research, and the compliance report — a findings table with the flagged text, the recommended wording, and what the dealer already decided. Card buttons hand a request to the chat (fix this finding, dismiss it in Hrizn, re-check); the assistant confirms before anything stored changes. Clients that do not render cards receive the same data as text — nothing is lost.
Cards are served from the same endpoint (
ui://hrizn/*.html resources); there
is nothing extra to install.
Connect manually
The easiest setup is the MCP page in Hrizn (/{your-group}/mcp): save dealerships, copy the Streamable HTTP with OAuth URL, and follow a client walkthrough. CLI and other clients only need that URL.
Legacy API keys (migration only)
Existing integrations may still use the REST MCP URL with anhzk_ API key from Dealership Manager → API (REST keys only — not the MCP page):
read profile is the safest starting point for API-key clients. Use another profile only when the key has the matching scopes.
Cursor (manual fallback)
Install Hrizn from Cursor Directory when you can. Otherwise add this to.cursor/mcp.json or Cursor Settings → Tools & MCP:
Claude Code (legacy API key)
Prefer the Hrizn Claude plugin. Add this only when OAuth is unavailable:OpenCode
For OAuth, addhttps://mcp.app.hrizn.io/mcp to your OpenCode MCP configuration and complete the Hrizn sign-in flow. Legacy API-key clients can use ?profile=read with the X-API-Key header.
Amazon Q / Kiro
Add an HTTP MCP server athttps://mcp.app.hrizn.io/mcp for OAuth. Legacy setups may use https://api.app.hrizn.io/v1/public/mcp?profile=read with X-API-Key.
OpenAI Codex (legacy API key)
Add this to~/.codex/config.toml only for API-key migration:
Try these prompts
- “Which rooftops am I connected to? Brief me on lot aging for the primary store.”
- “Find 2024–2025 RAV4s under $40k and outline a landing page from dealer context.”
- “Start an IdeaCloud on used hybrid SUVs, wait for research, then create content after I approve the selection.”
- “Check this ad copy for OEM compliance issues; don’t apply fixes until I confirm.”
- “Draft replies to unanswered 1–2 star reviews and publish only what I approve.”
- “Compare local days supply and flag price-cut candidates for 90-day trucks.”
- “Load dealer context and the top content opportunities so I can brief the creative team.”
- “Who are the sales managers at this store?”
- “Which published articles can I cite with a live URL?”
- “Create a model landing page for the 2026 Honda Civic Sport.”
- “Schedule a Facebook post for Saturday at 10:00 AM.”
Before making changes
Hrizn asks for confirmation before an AI assistant creates, publishes, updates, or removes anything. Review the proposed action carefully before approving it. Creating content through MCP can also update the same IdeaCloud and content workflows you use inside Hrizn.- Scheduled posts and event dates are sent as UTC timestamps. Tell the assistant your timezone (or let it confirm the dealership’s
suggested_timezone) so it converts correctly — it should never assume UTC. - Every tool description ends with the API scope it requires, so the assistant can tell you up front when a grant lacks access.
Security
- Save dealership grants only for rooftops you intend to expose to AI clients.
- OAuth tokens are scoped to your Hrizn account; revoke access from your AI client when no longer needed.
- Legacy API keys are shown once — treat them like passwords and revoke unused keys from Dealership Manager → API.
- Do not share media upload links.
Troubleshooting
- Grant required (403): Open MCP in Hrizn, select at least one dealership, save, then reconnect the client.
- The connection is unauthorized: Sign out and back in through the OAuth flow, or create a new legacy API key if you still use
hzk_auth. - Codex sign-in fails with
Unknown client: https://chatgpt.com/oauth/codex/…: The server URL differs fromhttps://mcp.app.hrizn.io/mcp(usually a trailing slash). Codex derives its OAuth client id from the URL, so fix the URL in~/.codex/config.tomlor the MCP settings and runcodex mcp login hriznagain. - ChatGPT/Codex callback “site can’t be reached” on
127.0.0.1: Auth0 finished; the local listener closed. Runcodex mcp login hriznand complete sign-in in that session. - A capability is unavailable: Check your plan (Teams+ for API Access, Unlimited for Market Maker and Social Hub writes) and the saved grant.
- A social account needs attention: Reconnect it in Dealership Manager → Social Profiles.
- A media upload link expired: Ask the assistant to start a new upload.
- The assistant can only search documentation: Connect Hrizn MCP at
https://mcp.app.hrizn.io/mcp, not a docs-only MCP. - New tools do not appear: Restart the AI client after saving a new grant or reconnecting OAuth.
