LabscoMCP early access ↗
hifriendbotMCP SERVER · OFFICIAL PROJECT

AiList MCP Server

Browse the AiList directory from chat — filter by category, sort by stars or views, see what is moving this week by star velocity, and submit or update your own listing with a key.

by hifriendbot ↗News, Feeds & Trend Monitoring✓ Official

LABSCO SUMMARY

A directory client where reading is open and editing belongs to whoever holds the key.

search_projects, get_project, list_categories, get_trending and get_stats all work with no credential, while submit_project and update_project gate on AILIST_API_KEY — and because update_project ties editing rights to the key a listing was created with, losing that key means losing the ability to correct your own entry. The other thing worth knowing is that get_trending sorts by star velocity rather than star count, so it answers what is gaining ground this week rather than what is biggest.

What it is

A client for the AiList project directory with 7 tools: search across the listings, full detail for one project, the category list with counts, this week's trending, directory statistics, and submitting or updating an entry.

What you get

  • Search that filters and sorts rather than only matching: search_projects takes query, category, built_with, page and per_page, and orders results by stars, trending, newest, name or views.
  • The category vocabulary as data: list_categories returns the available categories with project counts, so a filter value can be read off the directory instead of guessed.
  • One project in full: get_project takes a slug and returns the description, URLs, stats, category and tags for it.
  • Movement rather than totals: get_trending returns this week's projects sorted by star velocity, with limit setting how many come back.
  • Directory-level numbers: get_stats returns total projects, projects added this week, and the breakdown by category.
  • A write path for your own entry: submit_project takes name, tagline, description, url, github_url, npm_package, pypi_package, category, tags, built_with, creator_name and creator_url and goes live after an auto-review, while update_project revises an existing slug — both require AILIST_API_KEY, and update_project additionally requires that the listing was submitted under that same key.

Requirements

The read tools need nothing at all. submit_project and update_project require AILIST_API_KEY, and update_project also requires that the listing was created with that same key — ownership here is held by the key rather than by an account, so the key is what you need to keep.

Setup effort

One command — claude mcp add ailist -- npx -y ailist-mcp

See installation options