shadcn-exchange

endpoint

https://shadcn.exchange/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is shadcn-exchange live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is shadcn-exchange free to use?

Yes — the hub reached it with no key and no payment.

What tools does shadcn-exchange have?

4 tools: get_block, list_categories, list_registries, search_blocks.

Is shadcn-exchange safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_categories open 1h ago

  List the kinds of section the blocks are sorted into, such as hero, pricing, login, dashboard and footer, with how many blocks each has. Pass one to search_blocks as its category.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• list_registries open 1h ago

  List the public shadcn/ui registries whose blocks shadcn.exchange lists, the most blocks first, with how many of each are free and paid, what each one is, and its page. Pass a registry's id to search_blocks to search only its blocks.

  mcp-tool

  12345678910

  {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "maxLength": 80,
        "description": "Only registries with this in their id, name or description, such as dashboard or animated."
      }
    }
  }

  arguments 10 lines copy
• search_blocks open 1h ago

  Search the shadcn/ui blocks listed on shadcn.exchange: ready-made sections of a page, such as heroes, pricing tables, login forms, dashboards, footers and FAQs, from every public shadcn registry, free and paid. Use it when the user is building a page or a screen with shadcn/ui and wants a section to start from, or asks what blocks exist for something. Results come best first. Each has its id (for get_block), its description, its install command if it is free or where to buy it if it is paid, and its page with a live preview. Every word of the query has to be in a block's name, title, description or registry, so use one or two words, and the category for the kind of section.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 10,
        "maximum": 50,
        "minimum": 1,
        "description": "How many results to return, up to 50."
      },
      "price": {
        "enum": [
          "any",
          "free",
          "paid"
        ],
        "type": "string",
        "default": "any",
        "description": "free: blocks that install now with one command. paid: blocks their registries sell. any: both."
      },
      "query": {
        "type": "string",
        "maxLength": 80,
        "description": "One or two words to find, such as \"pricing\", \"sign in\", \"testimonials\" or \"bento\". Leave it out to list a category or a registry."
      },
      "offset": {
        "type": "integer",
        "default": 0,
        "maximum": 10000,
        "minimum": 0,
        "description": "How many results to skip, for the next page."
      },
      "category": {
        "enum": [
          "hero",
          "pricing",
          "dashboard",
          "login",
          "navbar",
          "sidebar",
          "features",
          "footer",
          "cta",
          "testimonials",
          "faq",
          "charts",
          "tables",
          "contact",
          "blog",
          "stats",
          "team",
          "logo-cloud",
          "gallery",
          "bento",
          "ecommerce",
          "chat",
          "file-upload",
          "404-page",
          "onboarding",
          "settings",
          "newsletter",
          "about",
          "careers",
          "changelog",
          "integrations",
          "banner",
          "timeline",
          "empty-state",
          "cookie-consent",
          "kanban",
          "portfolio",
          "coming-soon"
        ],
        "type": "string",
        "description": "The kind of section, from list_categories, such as hero, pricing, login, dashboard or footer."
      },
      "registry": {
        "type": "string",
        "maxLength": 64,
        "description": "Only this registry's blocks: its id from list_registries, such as efferd or shadcnblocks."
      }
    }
  }

  arguments 83 lines copy
• get_block unknown never probed

  Get one block's details by its id from search_blocks: what it is, its install command, the npm packages and registry items it depends on, the files it adds, and its registry's notes on using it. Set include_source to also get its source code, for when the user wants to read or adapt the code rather than install it.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "maxLength": 300,
        "minLength": 3,
        "description": "The block's id from search_blocks, as registry/name, such as efferd/hero-1. Its page's address works too."
      },
      "include_source": {
        "type": "boolean",
        "default": false,
        "description": "Also give the source of its files. It can be long, and installing the block adds the files anyway."
      }
    }
  }

  arguments 19 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.