Set up Col MCP

Search Col’s libraries and verified components from your coding agent.

Connect your client

Col hosts a read-only MCP server over Streamable HTTP. You need an MCP client with remote HTTP support; no Col account, API key, or local server is required.

https://collection-of-libs.vercel.app/api/mcp
Server URL

Choose your client below. Keep any servers already in its configuration.

Claude Code

With Claude Code installed, run this command to make Col available across your projects. Use --scope project instead of --scope user to save it in the current project’s .mcp.json.

claude mcp add --transport http --scope user col https://collection-of-libs.vercel.app/api/mcp
Claude Code command

Start a new Claude Code session and run /mcp to check the connection. See the Claude Code MCP docs.

Codex

With the Codex CLI installed, add Col and check that it is listed:

codex mcp add col --url https://collection-of-libs.vercel.app/api/mcp
codex mcp list
Codex commands

Alternatively, add this table to ~/.codex/config.toml:

[mcp_servers.col]
url = "https://collection-of-libs.vercel.app/api/mcp"
Codex config

Start a new session and run /mcp to see active servers. See the Codex MCP docs.

Cursor

Add the col entry to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects:

{
  "mcpServers": {
    "col": {
      "url": "https://collection-of-libs.vercel.app/api/mcp"
    }
  }
}
Cursor config

Open Cursor’s MCP settings and enable Col. Use it from an agent chat. See the Cursor MCP docs.

VS Code

Run MCP: Add Server in the Command Palette, choose HTTP, paste the server URL, and name it col. Choose .mcp.json for the workspace, or a global configuration for all projects.

For a portable workspace configuration, add this entry to .mcp.json at the project root:

{
  "mcpServers": {
    "col": {
      "type": "http",
      "url": "https://collection-of-libs.vercel.app/api/mcp"
    }
  }
}
VS Code config

Run MCP: List Servers, select Col, and start it. Enable its tools in agent chat. See the VS Code MCP setup guide.

Install the plugin

The optional Col plugin bundles the MCP connection with a UI component workflow skill. Choose the plugin or a direct connection to avoid adding Col twice.

claude plugin marketplace add screen-gd/Col
claude plugin install col@col
Claude Code plugin
codex plugin marketplace add screen-gd/Col
codex plugin add col@col
Codex plugin

See the plugin guide for package details.

Try the connection

Start a new agent session and confirm Col exposes search_libraries, search_components, get_library, and get_component. Then try:

Use Col to find a React command menu for a Tailwind CSS project.
Inspect the exact component and its library’s setup.
Link the official docs and tell me what is unverified.
Example prompt

Col returns source links and recorded setup guidance. Its component coverage is partial; missing entries do not mean a library lacks a component.

Troubleshooting

  • No tools listed: check the URL, enable Col in your client, and start a new session after changing configuration.
  • Connection failed: select HTTP, not a local command or SSE. Check your client’s server logs and network access to the endpoint.
  • A browser visit returns a method error: the endpoint expects MCP POST requests. Confirm the connection through your client instead.
  • An empty search result: shorten the query or adjust filters, then check the library’s official docs. Coverage is partial.