Claude Code

Add the Vuesax MCP server to Claude Code with one command.

Add the server

claude mcp add --transport http vuesax https://mcp.vuesax.com \
  --header "Authorization: Bearer vsx_your_key_here"

That is the whole setup. Verify it:

claude mcp list

You should see vuesax with a connected status. Inside a session, /mcp shows the server and its tools.

Scope

By default the server is added for the current project. Pick a different scope with -s:

# available in every project on this machine
claude mcp add -s user --transport http vuesax https://mcp.vuesax.com \
  --header "Authorization: Bearer vsx_your_key_here"

# committed to the repo in .mcp.json — shared with your team
claude mcp add -s project --transport http vuesax https://mcp.vuesax.com \
  --header "Authorization: Bearer vsx_your_key_here"
Careful with project scope -s project writes .mcp.json into the repository. Do not commit your key there — use an environment variable, or have each teammate add the server at user scope with their own key.

Keep the key out of the file

export VUESAX_KEY="vsx_your_key_here"

claude mcp add -s user --transport http vuesax https://mcp.vuesax.com \
  --header "Authorization: Bearer $VUESAX_KEY"

Install the skill

Once, at the start of a session:

Call get_vuesax_skill and install it.

Claude Code writes it to ~/.claude/skills/vuesax/SKILL.md. Restart, and from then on it knows the catalog’s conventions — where files go, how tokens and effects are wired, which component to reach for. See Skills.

Use it

Use the vuesax MCP: I need a settings page. Find a tabs component and a
switch, pull their source into src/components/ui/, and build the page.
Search vuesax animations for something ambient for a hero background,
show me three options with their descriptions, then pull the one I pick.

Remove it

claude mcp remove vuesax

If the tools don’t show up

  • Run claude mcp list — a failing server reports its error there.
  • Check the key starts with vsx_ and the account is PRO.
  • Restart Claude Code; MCP servers are loaded when the session starts.