Developers
Connect Aravi to Claude, ChatGPT, Cursor and your own agents over MCP — one integration, and every AI tool can read your brand, create on-brand, and check its work before publishing.
Your MCP server
One URL, every client. Interactive apps sign in with OAuth — no key needed. Headless agents and servers authenticate with an API key.
https://aravi-api-production.up.railway.app/api/mcp
Connect your client
Pick your tool, then your auth method — setup takes about a minute.
https://aravi-api-production.up.railway.app/api/mcp
Know it worked: after connecting, ask your assistant “List my Aravi brands” — you should see your workspace brands come back. Then try a starter prompt below.
Try these first
Copy a prompt into your connected assistant — each one exercises a different part of the brand layer.
What agents can do
The full tool surface agents get once connected.
Understand
aravi_get_brand_contextIdentity as a ready-to-inject text block — for on-brand copy and prose
Araviaravi_get_brand_contractStructured JSON contract — every field with confidence + provenance + version
Newaravi_get_brand_design_mdDESIGN.md design tokens for generating on-brand UI code
Araviaravi_get_brandFull four-layer identity (strategic, verbal, visual, imagery)
aravi_get_brand_auditMaturity score, missing signals, prioritized fixes
aravi_get_brand_assetsCanonical logo, style anchors, fonts, palette — real assets, not descriptions
Newaravi_list_brandsAll workspace brands with status and key facts
aravi_search_librarySemantic search over the brand image library
Create
aravi_create_brandOnboard a brand from a website URL or Instagram handle (~60–90s)
aravi_generate_imageOn-brand image generation — identity, anchors and logo injected automatically
aravi_get_imageCollect a generation (returns brand-match score with the URL)
aravi_list_imagesBrowse generated images
Guardrail
aravi_check_brand_fitScore any image or copy 0–100 against the brand — violations + fixes before you publish
NewAccount
aravi_get_accountAuthenticated user, workspace and plan
aravi_check_creditsRemaining generation credits
API keys
For headless agents, CI, and server-to-server calls. Keys are workspace-scoped and shown only once.
No API keys yet — interactive clients can use OAuth without one.
Brand-change webhook
Get a signed POST whenever a brand's identity changes — so your agents and caches invalidate instead of polling.
Payload: {event, brand_id, identity_version, updated_at} — HMAC-SHA256 signed via the x-aravi-signature header. HTTPS only; leave empty to disable.
How agents should use Aravi
This guidance is also served to agents automatically via MCP server instructions.
1. Find or onboard the brand — aravi_list_brands, or aravi_create_brand with a website URL or Instagram handle (~60–90s, poll with wait=true).
2. Read the layer — get_brand_context for copy, get_brand_design_md for UI code, get_brand_contract for structured data with confidence scores.
3. Create — describe the scene and intent; Aravi injects the identity, style anchors, and logo automatically. Collect with aravi_get_image — the result includes its brand-match score.
4. Guard before publishing — run aravi_check_brand_fit on anything made outside Aravi. Score ≥ 70 with no hard violations = on-brand.
Each generation costs 1 credit. Connected clients share your workspace's balance.