Mantine UI MCP Server

Created By
hakxela year ago
MCP server for working with Mantine UI components - provides documentation, generation, and theme utilities
Overview

What is Mantine UI MCP Server?

Mantine UI MCP Server is a Model Context Protocol (MCP) server designed to facilitate the use of Mantine UI components by providing documentation, generation, and theme utilities.

How to use Mantine UI MCP Server?

To use the server, you can install it globally via npm or run it using npx. Configuration is required for integration with applications like Claude Desktop or VS Code.

Key features of Mantine UI MCP Server?

  • Documentation Tools: Access detailed documentation for any Mantine component, search components by keyword, and list all available components.
  • Component Generation: Generate custom Mantine-based components with specified variants.
  • Theme Utilities: Create theme configurations for Mantine components, including light and dark mode settings.

Use cases of Mantine UI MCP Server?

  1. Quickly retrieve documentation for UI components during development.
  2. Generate custom components tailored to specific design requirements.
  3. Create and manage theme configurations for consistent UI styling across applications.

FAQ from Mantine UI MCP Server?

  • Can I use Mantine UI MCP Server with any project?

Yes! It can be integrated into any project that utilizes Mantine UI components.

  • Is there a cost to use Mantine UI MCP Server?

No, it is open-source and free to use under the MIT license.

  • What programming language is Mantine UI MCP Server built with?

It is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hakxel
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago