MCP

Connect Cursor or any MCP client to the Neura Kit catalog — search components, read props and examples, and pull recent changelog entries without leaving the agent.

What it is

Neura UI exposes a read-only Model Context Protocol server for the neura-ui/neura-kit library. Agents can look up real Blade tags, props, docs URLs, and release notes instead of inventing APIs.

The server is read-only and idempotent. It does not mutate your app. Today the HTTP endpoint has no auth middleware — treat it as a public documentation API.

Endpoint

The MCP route lives on the app domain (not the docs subdomain), via laravel/mcp :

TEXT

https://neuraui.dev/mcp/neura-kit

Transport is HTTP (POST ). You can also run the same server over stdio with Artisan when the client supports it:

Shell

php artisan mcp:start neura-kit

Prefer the HTTP URL in Cursor — stdio under some desktop runtimes (e.g. AppImage) can fail to spawn php cleanly.

Cursor setup

Add the server to .cursor/mcp.json (project) or your user MCP settings:

JSON

{
  "mcpServers": {
    "neura-kit": {
      "url": "https://neuraui.dev/mcp/neura-kit"
    }
  }
}

Reload MCP servers in Cursor, then ask something like “search Neura Kit for a file upload component” or “get props for neura::button”.

Tools

Four tools are registered on the Neura Kit server:

search-components

Free-text search by intent, name, prop, or keyword (e.g. file upload , date range ). Args: query (required), limit (1–25, default 10).

get-component

Full details: Blade tag, props with defaults, docs URL, and usage examples. Pass a slug (button ), label (File Manager ), or tag (neura::button ).

list-components

Browse the catalog, optionally filtered by category (Form Elements , Layout , Data Display , …).

get-changelog

Recent Keep a Changelog entries from the kit CHANGELOG.md . Arg: limit (1–20, default 5).

Suggested agent workflow

The server instructions nudge agents to resolve APIs before inventing them:

search-components — find the right component by intent
get-component — read the tag, props, and Blade examples
list-components — browse a category when exploring
get-changelog — check what changed in recent releases

Always use the returned Blade tag (e.g. neura::button , neura::alerts ) and documented props. Prefer soft / ghost variants and existing size / rounded / shadow packs over one-off CSS.