Join the waitlist
Aravi AI for VS Code

Your brand, in every Copilot suggestion.

Connect Aravi AI to VS Code over MCP. Copilot and other AI extensions read your brand's colors, typography, and spacing before they suggest code, right where you're already working.

Getting started

Connect VS Code to your brand in minutes

One entry in .vscode/settings.json. After that, Copilot and any MCP-compatible extension read your brand before suggesting a single line.

.vscode/settings.json
{
  "mcp": {
    "servers": {
      "aravi": {
        "type": "sse",
        "url": "https://mcp.araviai.com"
      }
    }
  }
}
  1. 1

    Ingest your brand

    Upload your guidelines, your site, or a deck. Aravi AI extracts your visual identity into structured, queryable rules.

  2. 2

    Add Aravi AI as an MCP server

    One entry in .vscode/settings.json. Works with Copilot and any MCP-compatible extension.

  3. 3

    Start coding

    AI completions and generations query your brand context automatically. Every color, font, and spacing value matches your brand.

Use cases

What to build with Aravi AI + VS Code

Copilot with brand context

Code completions that use your actual brand colors, font stacks, and spacing tokens, not generic defaults.

On-brand component generation

React, Vue, or HTML components that match your visual identity — no fixing colors and fonts after the AI writes the code.

Brand-aware inline suggestions

Suggestions in your editor respect your brand's CSS custom properties and design tokens automatically.

Cross-team consistency

Every developer gets the same brand context in their editor. No more one person shipping the wrong shade of blue.

FAQ

Aravi AI + VS Code, answered

Does this only work with GitHub Copilot?

No. Any MCP-compatible extension in VS Code can read the same brand profile. Copilot is just the most common one.

What does an extension read before it suggests code?

Your brand's colors, typography, spacing tokens, and visual conventions, structured from your brand profile.

Does every developer on the team need their own setup?

Each developer adds the same entry to their own .vscode/settings.json, or you share it through a workspace settings file, so the whole team reads the same brand profile.

Make VS Code fluent in your brand

Join the first group of brands giving VS Code a source of truth to read before it suggests.

Join the waitlist