Hrizn logo
ModelContextProtocol

MODEL CONTEXT PROTOCOL

Your Content OS in the AI tools you already use

hrizn mcp connect --client claude

Use Claude, Cursor, ChatGPT, Gemini, and other AI clients against the same live store you already manage inside Hrizn. As work spreads across assistants and agents, Hrizn MCP keeps rooftops and agency partners on one system of truth.

Clara using Claude Code connected to live Hrizn dealership data through Hrizn MCP
The Hrizn MCP server bridging AI clients with dealership tools and data

What Is Hrizn MCP?

Retail automotive marketing has always been a partnership: the rooftop owns the lot, the brand, and the local story; agencies and content partners scale execution across stores and campaigns. In an evolving AI landscape, that work is splintering — drafts in one chat, inventory checks in another, research in the app, approvals somewhere else. Generic assistants fill the gaps with guesses.

Hrizn MCP extends the Content Operating System into the AI environments where dealers and agencies spend more of their day — so external assistants work from Hrizn's content, data, and rules, not the open web.

Use one governed brief across the store and the agency desk

Ground every draft in live inventory and Dealer DNA

Run OEM Compliance Checking before content ships

Keep research, voice, inventory, and compliance connected

Works With the AI Clients Your Team Already Prefers

ClaudeClaude
CursorCursor
OpenAIChatGPT
GeminiGemini
ModelContextProtocolOther MCP clients
Join our newsletter
Stay Connected

Join our newsletter
Stay Connected

What You Can Do With Hrizn MCP Connected

Teams and partners work from the same live store, wherever the conversation happens

Share One Brief

Dealer profile, Dealer DNA, brand voice, staff, and categories — whether the user sits at the store or at an agency desk.

Create From the Same Research

IdeaCloud opportunities, question selection, and article settings stay aligned with Composer.

Ground Content in Live Inventory

Search stock, understand lot health, and use Hrizn vehicle descriptions in campaigns and copy.

Check Copy Before It Ships

Paste ads, landing pages, or social drafts into the assistant and run Hrizn's OEM Compliance Checking.

Publish With Context

Cite live content URLs, pull from content intelligence, and reflect Social Hub reputation in planning.

Bring Market Insight In

Pull Hrizn Market Maker competitive and pricing context directly into the assistant.

Manage Social Hub Workflows

Post and reply from the same governed social connections dealers already manage in Hrizn.

One System of Truth

External assistants work from Hrizn’s content, data, and rules — not the open web.

One OS for the Rooftop and the Partner Bench

Hrizn MCP is built for automotive organizations already running on Hrizn. Setup is guided in the product, with permissions that reflect how a store actually works — read and research for some roles, create, compliance-check, and publish for others.

The point is continuity: as AI becomes how shoppers discover stores and how teams produce campaigns, the Content Operating System should follow the user. Hrizn MCP is available now — dealers and agency partners connect inside Hrizn, and setup guides cover major AI clients.

claude_desktop_config.json

ModelContextProtocol

MCP

// Add Hrizn to any MCP client
{
"mcpServers": {
"hrizn": {
"command": "npx",
"args": ["-y", "@hrizn/mcp"],
"env": {
"HRIZN_API_KEY": "sk_live_••••••"
}
}
}
}

claude mcp add hrizn

Bring Your Content OS Into Every Assistant

Keep research, voice, inventory, and compliance connected as the industry moves faster — from the assistants your team and partners already use.