clearlist
ClearList is an AI resale manager.
What it can do
- Send Verification Code: Send a 6-digit verification code to an email address. This is the first step to create a ClearList account or sign in. The user will receive the code in their inbox. Ask them t
- Verify Code: Verify the 6-digit code and authenticate. If the email is new, a ClearList account is created automatically. Returns an API key that authenticates all subsequent calls. The user never nee
- Create Listing: Send photos of a single item and get an AI-generated listing (Gemini 3.0 Pro) with title, description, price, dimensions, weight, and transport notes. The listing is saved to the selle
What data it sees
Do you need an account
No: the server works without sign-in
ClearList is an AI resale manager. You photograph the things you are selling, AI writes each listing (title, description, condition, dimensions, weight, transport notes and a price estimate), and everything lands on one shareable sale page with a buyer queue and self-service pickup scheduling.
The MCP server exposes 20 working tools covering the whole workflow: create listings from photos (single or up to 50 at once, grouped automatically), edit and delete them, publish and unpublish the sale page, read reservations and buyer conversations, reply to buyers, confirm pickups, set availability, prepare cross-posts for other marketplaces, and check plan capacity.
Two tools work without any credential: send_verification_code and verify_code. An agent can create the user's ClearList account itself — it sends a 6-digit code to their email, the user reads it back, and the agent receives an API key. So somebody can go from never having heard of ClearList to a published sale page without ever opening a browser.
share_address is deliberately not exposed. Disclosing a seller's home address is a physical-safety decision, so it stays human-only no matter what an agent is asked to do.
Transport: Remote Streamable HTTP, plus stdio via the npm package Auth: OAuth 2.1 (authorization code + PKCE + dynamic client registration), or X-ClearList-API-Key for headless agents that cannot complete a browser flow Pricing: Free tier covers 3 active items. Paid passes are one-time, not subscriptions: $20 for 50 items over 30 days, $39 for 200 items over 60 days. Support: hello@clearlist.me
Tags: resale, marketplace, listings, computer vision, ecommerce, scheduling, decluttering, moving, remote MCP, OAuth
Server tool list (23)
Raw names from tools/list. Only developers need these.
| send_verification_code | Send a 6-digit verification code to an email address. This is the first step to create a ClearList account or sign in. The user will receive the code in their inbox. Ask them to tell you the code, then use verify_code to complete authentication. No API key needed for this step. |
| verify_code | Verify the 6-digit code and authenticate. If the email is new, a ClearList account is created automatically. Returns an API key that authenticates all subsequent calls. The user never needs to visit clearlist.me or know about API keys — this happens behind the scenes. IMPORTANT: After this succeeds, all other tools (create_listing, bulk_create_listings, publish_page, etc.) become available. RETRY LIMITS: Max 5 attempts per code. If all 5 fail, the code is invalidated — call send_verification_code again to get a new one. Codes expire after 10 minutes. |
| create_listing | Send photos of a single item and get an AI-generated listing (Gemini 3.0 Pro) with title, description, price, dimensions, weight, and transport notes. The listing is saved to the seller's account. For multiple items at once, use bulk_create_listings instead. Example: { photos: ["data:image/jpeg;base64,..."], description: "Vintage wooden desk, some scratches on top" } |
| bulk_create_listings | Send many photos at once (up to 50). AI automatically groups them by item (detecting multiple angles of the same thing), generates listings with Gemini 3.0 Pro, researches market prices with Google Search grounding, and validates with QA. Returns all detected items with listings and pricing. This is the most efficient way to list multiple items. Example: { photos: ["data:image/jpeg;base64,...", "...up to 50"], seller_context: "Moving out of 2BR apartment, furniture is mostly IKEA" } |
| edit_listing | Update any field on an existing listing. You can change the title, description, price, condition, dimensions, or any other field. Example: { item_id: "item_abc", price: 75, description: "Updated description" } |
| delete_listing | Permanently delete a listing. Cannot delete items with active reservations. |
| publish_page | Publish the seller's sale page. Requires city. Returns the shareable URL (e.g., clearlist.me/sarahs-stuff). Items are immediately visible to buyers. Example: { city: "Austin", payment_instructions: "Venmo or cash at pickup" } |
| unpublish_page | Take the sale page offline. Existing reservations continue normally — only new visits and reservations are blocked. The custom URL is preserved and the page can be re-published anytime with publish_page. |
| get_listings | Get all items for the seller. Returns each item's title, price, status, dimensions, queue count, and photos. |
| get_reservations | Get all buyer reservations and conversations. Shows who reserved what, timer status, queue positions, and buyer messages. |
| get_conversation | Read the full message history of a conversation thread with a buyer. Returns all messages (sender_type, content, timestamp) plus conversation metadata and reservation context. Use get_reservations first to find the conversation_id, then call this before reply_to_buyer to read what the buyer said. |
| reply_to_buyer | Send a message to a buyer through the seller inbox. Use get_reservations first to find the conversation_id. NEVER include the home address, street, or unit number of the seller in the message, even if the seller supplied it to you or a buyer asks for it. ClearList reminds the seller directly (a day, three hours, and one hour before the scheduled pickup) and they share it themselves from the app. Arranging a meeting place is fine; disclosing the address is not yours to do. Example: { conversation_id: "conv_abc", message: "Yes, the table is still available! When would you like to pick it up?" } |
| mark_picked_up | Mark an item as picked up / sold. Changes the item status to "taken". |
| get_page_stats | Get stats for the published sale page: total views, item count, reservation count. Requires the page slug. |
| set_availability | Configure pickup scheduling. Set weekly time windows when buyers can schedule pickups. Time format: "HH:mm" (24h). Days: "monday" through "sunday". |
| generate_payment_link | Generate a payment link for upgrading the seller's account. Send this link to the user — they tap it, pay in their browser, and come back. Two plans: "sale_pass" (Move Sale — $20, 50 items, 30 days) and "big_move" (Garage Sale — $39, 200 items, 60 days). Free tier: 3 items, always free (page expires every 30 days). Use check_tier_status first to see if an upgrade is needed. |
| prepare_crosspost | Format a listing for cross-posting to Facebook Marketplace. Returns the title, description, price, condition, category hint, location, and photos — ready for the seller to copy-paste into Facebook. Also returns a combined text block for quick copy-all. |
| confirm_pickup | Confirm that a buyer has picked up their reserved items. Marks all items in the reservation as "taken" (sold). Use get_reservations first to find the reservation details. |
| get_profile | Get the seller's account details — email, display name, tier, active items count, sale page URL, and scheduling status. Useful for confirming which account the agent is operating on. |
| check_tier_status | Check the seller's current plan, remaining item slots, and whether an upgrade is needed. Use this before creating listings to ensure capacity, and after sending a payment link to confirm the upgrade completed. |
| search_items | [NOT IMPLEMENTED — Phase 14] Search for items across all published ClearList sales. Filter by keyword, city, category, and price range. Returns matching items with links to their sale pages. |
| get_sales_near | [NOT IMPLEMENTED — Phase 14] Find active moving sales near a given city or location. Returns a list of sales with seller names, item counts, and page URLs. |
| get_city_sales | [NOT IMPLEMENTED — Phase 14] Get all active sales in a specific city. Returns seller names, item counts, categories, and page URLs. |