For AI assistants
Pantrix writes its own documents for coding assistants from its sources at every build: an MCP server, a skill, llms.txt and the whole library as JSON. An assistant asks for what it needs and gets the library as it is today, not a guess from Material.
What an assistant is given
https://pantrixui.com/mcp | The MCP server, which this site serves over HTTP: an assistant is given its address alone |
mcp-0.1.0-alpha03-all.jar | The same server as one jar that runs by itself, attached to each release, for a machine of your own |
pantrix-ui skill | The rules code written with Pantrix keeps, Material's names and Pantrix's, and how the parts fit |
llms.txt, llms-full.txt | The index of the documents, and all of them in one file, at this site's root |
pantrix-ui.json | The library as data: every component, its parameters, its examples and its tags |
Set it up
Give the assistant the server
The server answers at
https://pantrixui.com/mcp, so the assistant needs nothing but its address.Claude Code
claude mcp add -t http pantrix-ui https://pantrixui.com/mcpA project's .mcp.json
.mcp.json{ "mcpServers": { "pantrix-ui": { "type": "http", "url": "https://pantrixui.com/mcp" } } }Install the skill
The skill says what to do; the server says what the library is today. The two together are best. In Claude Code, Pantrix UI's plugin brings the skill, from the repository the library is distributed from:
claude plugin marketplace add develappsancho/pantrix-ui-cmp-package claude plugin install pantrix-ui@pantrix-uiOr run the server on your machine
The jar is attached to each release, and after
./gradlew publishToMavenLocalin the library's repository it stands in the local Maven repository too:~/.m2/repository/com/pantrixui/mcp/<version>/. It runs on JDK 17 or newer. It writes the skill into a project too, which the team then gets through git, and which any assistant that reads skills takes:curl -fL --create-dirs -o ~/.pantrix/mcp-0.1.0-alpha03-all.jar https://github.com/develappsancho/pantrix-ui-cmp-package/releases/download/v0.1.0-alpha03/mcp-0.1.0-alpha03-all.jar claude mcp add pantrix-ui -- java -jar ~/.pantrix/mcp-0.1.0-alpha03-all.jar java -jar ~/.pantrix/mcp-0.1.0-alpha03-all.jar skill .claude/skills
Where the files are
| What | Where |
|---|---|
| The MCP server | https://pantrixui.com/mcp, mcp-0.1.0-alpha03-all.jar on the release, or the local Maven repository after a local publish |
| The skill | Claude Code's plugin pantrix-ui@pantrix-ui, pantrix-ui-skill-0.1.0-alpha03.zip on the release, or the jar's skill command |
llms.txt | https://pantrixui.com/llms.txt: its links lead to this site's pages, and what has no page is under /llms/ |
| Every document, on your machine | java -jar mcp-0.1.0-alpha03-all.jar docs <folder> |
What it can ask
search_components, get_component | A component by what it is for, and its page with examples that compile |
get_component_metadata | Its import, its artifact, its tags and every parameter |
search_api, get_api | Any declaration, by its name or by what it does |
get_example, list_examples | One example's code with its imports |
search_documentation, get_documentation_page | The pages, the guides and the skill's references |
get_changelog | What changed, version by version |
get_rules | The skill itself, for an assistant that has not installed it |
Where next
- Teaching Pantrix to an assistant: How the documents are made, and what stops the build.
- Installation: The library's own dependency lines.
- detekt rules in your app: The rules a machine keeps after the assistant.
- Changelog: What `get_changelog` gives.