Arena by Dravensoft over MCP: the router, the references and every component document.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
Arena by Dravensoft
One design system, in React and in Angular, from one contract.
MIT License · Token-driven design system for React, Angular and Tailwind.
What you get
Components with a contracted API. The same components under both framework
names, rendering the same pixels, over one shared Tailwind layer. What a member
is called, what it takes, what it defaults to and what it means are written in
contracts/api/, and each layer's types and tables
are generated from there, so the two layers cannot drift apart quietly. Every
value a component draws resolves through a design token, so no hex and no bare
pixel sits anywhere inside one.
Accessibility bound per component instead of audited per release. Each
component declares which pattern it implements, most of them from the
WAI-ARIA Authoring Practices: the
roles it carries, the keys it answers, where focus lands, what dismisses it. A
requirement it does not meet yet is recorded beside it with its reason, and
bun run check:behaviour fails on the day a component stops answering the
pattern it named.
A style kernel, which is what a project answers to look like itself. The
questions about shape, space, weight and depth are Arena's; the answers are a
style plugin the project writes, and the appearance Arena installs with is one
such plugin rather than a floor under them. Palettes and fonts sit in an
arena.config.json, which the arena-to-prod command each package ships turns
into the one stylesheet a package cannot carry: Arena carries the language and
never the skin, and none of its own colours reach your build.
Metadata for a product that has to be found, which most products do not. The
Angular layer writes the document <head> from the routes it is handed, at
@dravensoft/arena-angular/metadata: title composition, a description, a
canonical and the og:* pair, with no route indexed until it says so. That
import path is a second entry point, so a project that never asks for metadata
never installs the router behind it. React writes no <head> at all, and both
layers publish the breadcrumb trail they draw in schema.org terms.
Eight products, drawn twice
The benches are a set of templates that implement
Arena: Calendly, ClickUp, Duolingo, Etsy, Grafana, Instagram, Notion and Superhuman, each mocked
twice, once in React and once in Angular, from one arena.config.json and one design/ directory
per pair. Every half installs Arena from npm and answers a style plugin of its own, so what a pair
shows is a project's appearance rather than Arena's, and the two halves of a pair are the same
screen under both framework names. That address is where they run, and
dravensoft-dev/arena-web-benches is where
they are written.
Why an agent can operate it
An API is a contract file rather than a paragraph, and so is the pattern a component binds and the role a style plugin answers; a gate holds the code, the documentation and the published packages to them. An agent handed this repository does not guess at Arena: it reads the contract that governs what it is about to write, and the gate tells it when it got it wrong.
That is also what makes the rules enforceable rather than aspirational. Each of
these is decided in contracts/design/AGENTS.md
and handed to a builder by
skills/design/SKILL.md, which states each one in
full and says which of them a gate reads your own sources for.
- Tokens are the only styling layer.
- Put no class of your own on an Arena component.
- Danger is outline, never filled.
- One primary accent per view.
- No gradients, on any surface.
- No emoji, in product or in copy.
- Icons are Phosphor class-name strings, never elements and never SVG.
- Never wrap an Arena component in your router's own link.
- An anchor Arena draws splits its activations.
- A press that starts on a control keeps to that control.
- Two themes, dark first.
- A chart carries identity or meaning, never both.
- Copy is English, formal and direct.
- A required member absent is a caller bug.
- No render follows from whether you bound a listener or filled a slot.
- A few components answer with a method rather than a member.
Install
That is the whole install. Phosphor is a peer rather than a second command, because Arena renders icon class names and never SVG; the layer page below says which peers each package declares.
Then write arena.config.json, run npx arena-to-prod (or bunx, or
pnpm exec), and import what it writes. frameworks/react/PACKAGE.md and
frameworks/angular/PACKAGE.md are the whole
of it, and they are the pages npm shows.
Over MCP
@dravensoft/arena-mcp is where the language travels. It serves the router, the
references and every component document to an agent that speaks the Model
Context Protocol, as resources and as tools, and the layer it serves is the one
your project installed. The component packages carry the code, the stylesheets
and the contracts your own markup answers to, and none of the prose.
A corpus and the components it describes are two packages and two version
numbers, so they can disagree. arena_start reads the version of the Arena
package in your project, compares it with the server's, and says so when the two
differ. Where they do, the components are right and the text is old.
As a Claude Code plugin
Update
A version means one commit. Each release is served from its git tag, with
the marketplace entry pinning source.ref to vX.Y.Z.
As a standalone Agent Skill
Hand any agent skills/design/SKILL.md. It is the
router, and it answers each question with one file. It routes over this tree,
so an agent handed the file alone has the questions and reaches the answers by
URL; one handed the clone or the plugin reaches them by path.
A component package is code, and the language reaches an agent by one of the three routes above. Install the MCP server, install the plugin, or hand over the skill, and the agent gets the guidelines, the contracts and every component's usage document, which is what turns "integrate Arena" into a task it finishes on its own.
See it
arena.dravensoft.org carries the design guidelines, the kitchen sink, and a playground page for every component, with no clone and nothing to install.
The same pages come up locally with bun run demos, from the same list, and
scripts/build/AGENTS.md says what a fresh clone
has to build before they mean anything.
An agent reads llms.txt first, which
routes to the rules of the language and then to one corpus per framework,
React and
Angular. They are separate on purpose: every
component ships under both names and the two documents are not interchangeable.
Dependencies
- Fonts are self-hosted, and no CDN request is made. Arena ships the Archivo
/ Familjen Grotesk / Spline Sans Mono
.woff2binaries inassets/fonts/, andcontracts/design-generated/fonts.generated.cssdeclares them with@font-face, so they load from the same origin as the page that reads them. A package consumer names their own three families inarena.config.json, wheresrcis either a stylesheet URL or a binary they host. - Icons are Phosphor Icons (MIT), and are not
bundled. Install the official package by default, either
@phosphor-icons/web(webfont) or@phosphor-icons/react, for full weight and tree-shaking flexibility. The CDN is a prototype-only convenience, not the default. See Iconography.
Which version am I getting
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Arena
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/arena)HTML Embed
<a href="https://allmcps.com/mcp/arena"><img src="https://allmcps.com/api/badge/arena?style=directory" alt="Arena on AllMCPs" /></a>