neobrutalism

The Neobrutalism MCP Server exposes a set of AI tools that allow assistants to interact with the Neobrutalism component library. It provides programmatic access to the component catalog, including the ability to list available components, fetch source code for a specific component, view demo usage, and inspect metadata such as dependencies and types. Additionally, you can browse the repository structure to understand how components are organized. Tools available include: list_components, get_component, get_component_demo, get_component_metadata, and get_directory_structure. You can integrate these tools into your AI prompts to generate UI code, prototypes, or design-system patterns based on Neobrutalism components. To use it, start the MCP server and configure your agent or tool to point at the server’s mcpServers.neobrutalism endpoint, then call the provided actions as part of your workflow.

Prerequisites:

• Node.js (LTS version) and npm installed on your machine.
• Internet access to install the MCP server package.

Installation options:

1. Quick start with npx (no global install required):

npx neobrutalism-mcp-server

2. Global install (optional):

npm install -g neobrutalism-mcp-server
neobrutalism-mcp-server

3. Install locally in a project (alternative):

mkdir my-mcp-project
cd my-mcp-project
npm init -y
npm install neobrutalism-mcp-server
npx neobrutalism-mcp-server

If you are integrating with Claude Code or other AI tools, you can use the npx approach to run the server on demand without a persistent installation.

Tips and considerations:

• The server is accessed via the npx command: npx neobrutalism-mcp-server.
• No special environment variables are required by default, but if you plan to run multiple MCPs or customize endpoints, you may extend or override config as needed.
• Ensure your environment has network access to fetch the package from npm when using npx or npm install.
• The server exposes a suite of utilities for component exploration, so you can build prompts that request specific components, demos, or metadata for rapid UI prototyping.
• When deploying in production, consider caching frequent component queries to reduce latency and API usage.