Antd Components Mcp

Created By
zhixiaoqianga year ago
Overview

What is Antd Components MCP?

Antd Components MCP is a Model Context Protocol (MCP) server designed to provide documentation for Ant Design components to large language models (LLMs) like Claude. This server allows LLMs to explore and understand Ant Design components through a set of dedicated tools.

How to use Antd Components MCP?

To use the MCP server, you can clone the Ant Design repository and run the extraction command to obtain the latest or specific version of the component documentation. You can also integrate it with the Claude desktop application by configuring the claude_desktop_config.json file.

Key features of Antd Components MCP?

  • Preprocessed data ready to use (preprocessed version is Ant Design V5.24.6 as of 2025/4/12)
  • Lists all available Ant Design components with names, descriptions, available versions, and usage information
  • View specific component documentation with filtered content for better context
  • Access specific component properties and API definitions
  • View code examples for specific components
  • Access update logs for specific components
  • Extensive caching to alleviate IO pressure

Use cases of Antd Components MCP?

  1. Providing LLMs with up-to-date Ant Design component documentation.
  2. Assisting developers in understanding component usage and properties.
  3. Facilitating the integration of Ant Design components into applications through LLMs.

FAQ from Antd Components MCP?

  • How do I extract the latest component documentation?

You can extract the latest documentation by running the command npx @jzone-mcp/antd-components-mcp extract [ant design repo path] after cloning the Ant Design repository.

  • Can I use this MCP server with other UI libraries?

Currently, it is designed for Ant Design, but there are plans to consider compatibility with other UI libraries in the future.

  • What are the benefits of using this MCP server?

It allows for faster server startup, smaller package size, and easier updates when new versions are released.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zhixiaoqiang
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
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.

8 hours ago