@striderlabs/mcp-poshmark
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEADLESS | No | Optional: set to 'false' to show browser window during local development. Default is 'true'. | true |
| POSHMARK_EMAIL | No | Email for Poshmark account. Required for authenticated actions (get_my_closet, create_listing, get_offers, accept_offer). | |
| POSHMARK_PASSWORD | No | Password for Poshmark account. Required for authenticated actions. | |
| BROWSERBASE_CDP_URL | No | Optional Browserbase CDP URL for cloud browser (falls back to local Playwright). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Search Poshmark for fashion listings by keyword, brand, category, size, and price range |
| get_listing_detailsA | Get full details of a specific Poshmark listing by ID or URL |
| get_my_closetA | List items in a Poshmark closet (defaults to authenticated user) |
| create_listingB | Create a new listing in the authenticated user's Poshmark closet |
| get_offersB | View offers received or sent on Poshmark listings |
| accept_offerA | Accept an offer received on one of your Poshmark listings |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: searching, viewing details, listing closet items, creating listings, viewing offers, and accepting offers. There is no overlap or ambiguity among them.
All tools follow a consistent verb_noun pattern (search_listings, get_listing_details, get_my_closet, create_listing, get_offers, accept_offer). The naming is uniform and predictable.
The server has 6 tools, which is well-scoped for a Poshmark integration covering search, listing management, and offer handling. Each tool serves a clear purpose without redundancy.
The tool set covers core operations like search, get details, list closet, create listing, and manage offers, but lacks update/delete for listings and decline/counter for offers. These are notable gaps in the full lifecycle.