Cursor

Wire the Vuesax catalog into Cursor's agent through mcp.json.

Add the server

Cursor reads MCP servers from a JSON file. Two places:

  • ~/.cursor/mcp.json — every project on this machine.
  • .cursor/mcp.json in the repo root — this project only.
{
  "mcpServers": {
    "vuesax": {
      "url": "https://mcp.vuesax.com",
      "headers": {
        "Authorization": "Bearer vsx_your_key_here"
      }
    }
  }
}

Save, then reload Cursor. Under Settings → MCP the vuesax entry should show a green dot and list its tools.

Don't commit the key If you use the project-scoped file, add .cursor/mcp.json to .gitignore. Anyone holding the key can spend your quota.

Use it

MCP tools run in the agent, so use Agent mode (⌘I), not inline edit:

Use the vuesax MCP: list components in the Overlay category, then pull the
dialog into src/components/ui/ and replace our current modal with it.
Search vuesax sections for a pricing block with a monthly/annual toggle,
add it to src/pages/pricing.vue and bind it to our Stripe plans.

Cursor asks for approval the first time a tool runs. You can allow the server for the session from that prompt.

Install the skill

Call get_vuesax_skill and save it as a Cursor rule.

Cursor’s rules live in .cursor/rules/. Saving the skill there makes the catalog’s conventions apply to every later request in the project — file placement, token wiring, which component fits which job. See Skills.

If the tools don’t show up

  • The JSON must be valid — a trailing comma silently disables the whole file.
  • Reload the window after editing (Developer: Reload Window).
  • Check the header block is headers, not env; this is an HTTP server, not a command.
  • Confirm the key is PRO and starts with vsx_.