Col
–

Col MCP for agents

Connect once, find a component, then implement from its official documentation.

Set up the connection

Give this prompt to an agent that can configure your coding client. Setup is complete when the client connects and lists all four Col tools.

Set up Col MCP for the coding client I use.
Read https://collection-of-libs.vercel.app/mcp for client-specific instructions.
Ask which client and configuration scope I want if they are unclear.
Add a server named col using Streamable HTTP at https://collection-of-libs.vercel.app/api/mcp.
Inspect the current configuration first. Preserve all existing servers and settings.
If Col is already configured directly or through its plugin, reuse that connection.
No credentials or authentication headers are needed.
Tell me if I need to restart the client or enable the server myself.
Confirm the connection lists search_libraries, search_components, get_library, and get_component.
If you cannot access the client’s tools, explain how I can verify them; do not claim the connection was tested.
Agent setup prompt

Find a fit

Inspect the project’s framework, styling, and existing components first. Call search_libraries with the requirement and hard filters. Every stack filter must match; use-case filters match at least one selected use case.

{
  "query": "command menu",
  "stacks": [
    "React",
    "Tailwind CSS"
  ],
  "limit": 5
}
search_libraries arguments

Use returned slugs for library lookups. Read matchedComponents and evidence.gaps before choosing a candidate. Search calls accept limit from 1 to 25 and a non-negative offset; use total to decide whether another page is needed.

Inspect the component

Call search_components with a documented name or alias. Optionally restrict the search to a library slug:

{
  "query": "command palette",
  "library": "shadcn-ui",
  "limit": 5
}
search_components arguments

Pass the exact returned ID to get_component, then use get_library for the library’s setup, pricing, documentation, and recorded compatibility.

{
  "id": "shadcn-ui/Command"
}
get_component arguments
{
  "slug": "shadcn-ui"
}
get_library arguments

Component IDs are case-sensitive. Copy them from search results rather than constructing them. An unknown ID or invalid filter returns a tool error.

Use the evidence

  • Keep evidence.verification and evidence.gaps in the recommendation. A verified component link does not verify every API, dependency, or variant.
  • A missing component means it has not been recorded. Do not infer support from generic tags or treat an empty result as proof of absence.
  • Compatibility is supported, unsupported, or unknown. Keep unknown constraints explicit and verify them against official documentation.
  • Deep documentation snapshots may be absent. Follow the returned source URLs for current installation, API, examples, versions, and licensing.

Implement in the project

  • Read the chosen component’s official docs and confirm they fit the project’s versions and styling.
  • Apply registry prerequisites before installation. Install only what the selected component needs and follow the project’s conventions.
  • Run the project’s relevant checks. Report the component, sources used, and anything that remains unverified.

Col supplies catalogue evidence. The coding agent performs project changes; the Col server does not read or modify the project.