Aicanvas MCP server

Read from the package source without running it. The installed server may list more.

• get_component

  Return the complete record for a single component: metadata + the entire .tsx source code as a string. Use after the user picks one from a search/list result and wants to see the implementation, or before installing if they want to inspect first. The source is the exact file the CLI install would write into a project.

• get_install_command

  Return the shadcn CLI command to install a single component into the user's project. After calling this, suggest the user run the command (or run it yourself if you have shell access). Requires shadcn-aware setup (Tailwind v4, components.json). For projects without that, fall back to `get_component` and write the file manually.

• get_system

  Return all files for a design system in a single response (every component, plus shared tokens and utilities), ready to write into the user's project. Use when the user wants to adopt a whole system rather than pick individual components.

• get_template

  Return all files for a single template: the example composition plus every component it uses plus shared tokens. Use for "I want exactly this dashboard" / "give me the entire mission-control screen". One CLI command installs all files.

• list_categories

  Return every category in the AI Canvas standalone component library, with the number of components in each. Use to orient before listing or searching, e.g. "what kinds of components are available?"

• list_components

  Return AI Canvas components, optionally filtered by category. Use after `list_categories` to drill into one, or pass no filter to browse everything. Each result includes slug, name, description, categories, screenshot URL, install command, and homepage URL, enough to evaluate without a separate `get_component` call. Pagination via `limit` and `offset`.

• list_systems

  Return every design system available on AI Canvas. A design system is a coordinated set of components plus shared tokens and utilities, installable in one CLI command. Use when the user asks about "themes", "design systems", or wants more than a single component.

• list_templates

  Return every ready-made template on AI Canvas. A template is a complete example screen built from one design system (a dashboard, a console, a control room), installable in one CLI command. Use to discover what full screens exist before fetching one with `get_template`, or when the user asks for "a dashboard" / "an admin screen" rather than a single component.

• search_components

  Fuzzy keyword search across standalone components, design-system components, AND ready-made templates (whole example screens). Matches on slug, name, description, categories, and tags; returns best matches ranked by relevance. Use when the user describes what they want in their own words, e.g. "an animated card stack", "background with waves", "a mission control dashboard". Results include screens

• Code scan2 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Aicanvas: common questions

Is Aicanvas MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Aicanvas safety report

How do I install Aicanvas?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Aicanvas need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Aicanvas maintained?

The last commit was in the last day (2026-09-19). The latest release is v0.2.5.

What can I use instead of Aicanvas?

Servers from other publishers that do the same job: Webcomponents React MCP server.