Clearlist

io.github.Cuneiform-LLCPublished by GitHub account Cuneiform-LLCv0.10.0Updated Oct 30, 2026

AI resale manager. Photograph an item, AI writes the listing, publish a sale page, manage pickups.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

ClearList MCP server lets an AI assistant run an online resale business: turn photos into listings, publish a sale page, and handle buyer reservations.

What you can do
  • Create and manage listings: generate listings from 1-5 photos or bulk-process up to 50 photos, then edit or delete items
  • Publish and manage the sale page: publish with a city, take it offline, and view page views and reservation stats
  • Handle buyers: read reservations and message threads, reply to buyers, confirm pickups and mark items sold
  • Configure selling: set pickup availability windows, prepare cross-posting text for Craigslist or Facebook, and read profile and subscription tier
  • Discover sales: search items by keyword, city, category or price, and find active sales near a location or in a city
  • Onboard an account: send an email verification code and verify it to create an account and…
When to use it
Useful when someone wants to sell household items or run a garage-sale-style listing through conversation, including bulk photo intake, pricing, publishing a shareable sale page and coordinating pickups with buyers. Also suited to browsing nearby sales.
Requirements
Runs as a remote endpoint at clearlist.me or as a local npm package (@clearlist/mcp-server) over stdio, which needs Node.js and a build step. Authentication is OAuth or an API key in CLEARLIST_API_KEY; without a key the agent can create an account via email verification. CLEARLIST_API_URL optionally overrides the API base URL.
Before you install
The server creates accounts and API keys on the user's behalf, and the key is held in memory for the session. Tools write and delete data: listings are permanently removed, pages are published publicly, and messages are sent to buyers. It also generates Stripe payment links for paid subscription upgrades. Photos and listing data go to the ClearList service and its AI backend.

Installation

In SourceWeft

  1. Open Clearlist in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Cuneiform-LLC%2Fclearlist/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "clearlist": {
      "type": "http",
      "url": "https://clearlist.me/api/mcp"
    }
  }
}

README

ClearList MCP Server

[LightNow capabilities]

AI agent interface to ClearList, an AI resale manager. Any MCP-compatible agent (Claude, ChatGPT, Gemini, Manus, custom agents) can create listings, publish sale pages, and manage reservations — all through the same API routes the web UI uses.

Users never need to visit clearlist.me. The agent handles account creation, photo processing, listing generation, and publishing entirely through conversation.

Quick Start

bash
cd mcp-servernpm installnpm run build

CLI

The package also ships a clearlist command-line tool for scripting seller actions directly against the REST API — no MCP host required:

bash
npm install -g @clearlist/mcp-server
clearlist login [email protected]        # send a 6-digit sign-in codeclearlist verify [email protected] 123456  # store the API key in ~/.clearlist/config.jsonclearlist items                        # list your listingsclearlist publish --city "Austin"      # publish the sale page, get the URLclearlist reservations                 # who reserved whatclearlist reply <conversationId> "Yes, still available"clearlist picked-up <itemId>           # mark an item soldclearlist status                       # plan, capacity, expiry

Every command prints JSON (pipe to jq for scripting). CLEARLIST_API_KEY overrides the stored key; CLEARLIST_API_URL overrides the default https://clearlist.me. Run clearlist help for the full reference.

MCP Apps (interactive UI)

get_listings, publish_page, and get_reservations declare an MCP Apps view (ui://clearlist/app.html) via _meta.ui.resourceUri. Hosts that render MCP Apps (ChatGPT, Claude.ai) show a listings gallery, a publish success card, or a reservations summary inline; hosts without UI support ignore the metadata and get the same JSON as before. View sources live in src/ui/views/ and are bundled into src/ui/generated-views.ts with npm run build:ui.

Two Ways to Connect

Option A: New user (no account yet)

No API key needed. The agent creates the account through conversation:

json
{  "mcpServers": {    "clearlist": {      "command": "node",      "args": ["/absolute/path/to/mcp-server/dist/index.js"],      "env": {        "CLEARLIST_API_URL": "https://clearlist.me"      }    }  }}

The agent uses send_verification_code + verify_code to authenticate. An API key is generated automatically and stored in memory for the session.

Option B: Returning user (has API key)

If the agent already has a key from a previous session:

json
{  "mcpServers": {    "clearlist": {      "command": "node",      "args": ["/absolute/path/to/mcp-server/dist/index.js"],      "env": {        "CLEARLIST_API_URL": "https://clearlist.me",        "CLEARLIST_API_KEY": "cl_your_api_key_here"      }    }  }}

All tools work immediately — no onboarding needed.

How It Works (The Grandma Flow)

Grandma → ChatGPT: "I'm moving, help me sell my stuff"ChatGPT: "Sure! What's your email?"Grandma: "[email protected]"
    [agent calls send_verification_code({ email: "[email protected]" })]
ChatGPT: "I sent you a 6-digit code. Check your email."Grandma: "482019"
    [agent calls verify_code({ email: "[email protected]", code: "482019" })]    → account created, API key returned, all tools unlocked
ChatGPT: "Account created! Now send me photos of everything you want to sell."Grandma: [sends 20 photos]
    [agent calls bulk_create_listings({ photos: [...20 photos] })]    → AI groups by item, generates listings, researches prices, validates
ChatGPT: "I found 12 items. Here's what I got:          1. IKEA Kallax Shelf — $45 (Good condition)          2. KitchenAid Mixer — $120 (Like New)          ...          Want me to publish your sale page?"
Grandma: "Yes! I'm in Austin."
    [agent calls publish_page({ city: "Austin", state: "TX" })]
ChatGPT: "Done! Your sale page is live at clearlist.me/grandmas-sale          Share this link on Facebook or Nextdoor."

Grandma never visited a website. Never generated an API key. Never created an account manually.

Available Tools (24)

Onboarding Tools (2) — No API key required

ToolDescription
send_verification_codeSend a 6-digit code to an email address
verify_codeVerify the code, create account if new, get API key

Seller Tools (19)

ToolDescription
create_listingSend 1-5 photos → AI generates listing → saves to account
bulk_create_listingsSend up to 50 photos → AI groups, generates, prices, QA-checks → saves all
edit_listingUpdate any field on a listing
delete_listingPermanently remove a listing
publish_pagePublish sale page with city, get shareable URL
unpublish_pageTake sale page offline
get_listingsList all items with status, price, queue count
get_reservationsSee buyer reservations, messages, timer status
get_conversationGet full message thread with a specific buyer
reply_to_buyerSend message to a buyer
mark_picked_upMark item as sold
confirm_pickupConfirm a scheduled pickup
get_page_statsPage views, item count, reservation stats
prepare_crosspostGenerate cross-posting content for Craigslist/Facebook
set_availabilityConfigure pickup scheduling windows
get_profileGet account profile and tier info
check_tier_statusCheck subscription tier and limits
generate_payment_linkGenerate Stripe payment link for upgrades

Discovery Tools (3) — Phase 14

ToolDescription
search_itemsSearch items across all sales by keyword, city, category, price
get_sales_nearFind active sales near a location
get_city_salesBrowse all sales in a city

Architecture

User (via any AI agent)  │  ▼Agent (ChatGPT, Claude, Gemini, Manus, etc.)  │  ▼ClearList MCP Server (this package)  │  stdio transport  │  ▼ClearList API Routes (/api/*)  │  HTTP + X-ClearList-API-Key header  │  ▼Firebase (Firestore, Auth, Storage) + Gemini AI

The MCP server is a thin protocol adapter. Zero business logic — everything lives in the API routes.

Authentication Flow

                    ┌─────────────────────────────────┐                    │   Agent starts (no API key)      │                    └─────────────┬───────────────────┘                                  │                    ┌─────────────▼───────────────────┐                    │  send_verification_code          │                    │  POST /api/auth/send-code        │                    │  { email: "[email protected]" }     │                    └─────────────┬───────────────────┘                                  │  ← email sent with 6-digit code                    ┌─────────────▼───────────────────┐                    │  verify_code                     │                    │  POST /api/auth/verify-code      │                    │  { email, code, agent: true }    │                    └─────────────┬───────────────────┘                                  │  ← creates account + returns API key                    ┌─────────────▼───────────────────┐                    │  API key stored in memory        │                    │  All subsequent calls use it     │                    │  X-ClearList-API-Key: cl_xxx     │                    └─────────────────────────────────┘

Development

bash
# Type-checknpm run type-check
# Buildnpm run build
# Run directly (for testing)CLEARLIST_API_URL=http://localhost:3000 npm run dev

Source: mcp-server/README.md at commit bc7274c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v0.10.0LatestOct 15, 2026
  2. v0.9.24Sep 23, 2026
  3. v0.9.22Sep 17, 2026
  4. v0.9.21Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts