AI & MCP
Slate is built so agents can read real Blade APIs instead of inventing React/shadcn. Use the docs index, the MCP server, or a Cursor rule.
llms.txt
Point tools that support llms.txt at:
- https://slate.electrik.dev/llms.txt — curated index of docs, components, blocks, and examples
- https://slate.electrik.dev/llms-full.txt — index plus concatenated markdown
Component pages also ship as markdown:
https://slate.electrik.dev/components/button.md
Docs page actions include View as Markdown and Open in ChatGPT / Claude / v0 / Scira with the live page URL in the prompt.
MCP server (read-only)
Slate exposes the same read-only MCP tools in two ways:
- Remote (Cloudflare) — paste a URL into Cursor (no local Node process)
- Local (npm) —
npx @electrik/slate-mcpover stdio
Both can:
- list shipped components and blocks
- fetch component docs (markdown)
- fetch Blade source from the
3.xbranch on GitHub - pull
llms.txt
They do not install packages. Slate is Composer-based:
composer require electrik/slate:^3.0@@alpha
Cursor — remote MCP (recommended)
After the Worker is deployed (mcp/worker in the Slate repo):
{
"mcpServers": {
"slate": {
"url": "https://mcp.slate.electrik.dev"
}
}
}
Optional custom domain later: https://mcp.slate.electrik.dev (configure in Cloudflare Worker settings).
Cursor — local npm
{
"mcpServers": {
"slate": {
"command": "npx",
"args": ["-y", "@electrik/slate-mcp"]
}
}
}
npm install -g @electrik/slate-mcp
# or one-shot:
npx -y @electrik/slate-mcp
Optional env:
| Variable | Default | Purpose |
|---|---|---|
SLATE_DOCS_URL |
https://slate.electrik.dev |
Docs / markdown base |
SLATE_SOURCE_URL |
GitHub raw 3.x |
Blade source base |
Example prompts
- List Slate form components and show me the input docs
- Fetch the dialog Blade source and build a confirm flow
- Use the login block pattern with progressive field props
Cursor rule
Copy AGENTS.md into your app, or add .cursor/rules/slate.mdc from the Slate repo. It covers progressive props, anonymous Blade, tokens, and Livewire patterns.