mcp server
Swell MCP
Model Context Protocol server for Swell e-commerce platform integration with AI assistants
Description as published by the maintainer. Source
- version 1.1.0
- active
- workflow automation
active — Most recent push to the repository was 2026-05-15. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 2 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-05-15 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 12 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-15 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-15 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
com.getmunin/munin
— last commit 2026-08-06, shares headless
Open-source all-in-one MCP-first customer platform: KB, Conversations, CRM, CMS, Outreach, Analytics
-
io.github.browser-gateway/browser-gateway
— last commit 2026-08-04, shares headless
AI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.
-
Screaming Frog SEO Spider MCP Server
— last commit 2026-06-12, shares headless
Crawl websites, export SEO data, and manage crawls via Screaming Frog SEO Spider.
-
ellmos Blender Use
— last commit 2026-08-04, shares headless
Headless Blender asset QA over MCP: background script runs and FBX reimport verification.
-
ai.pullpush/pullpush-mcp
— last commit 2026-07-30, shares ecommerce
Connect any two APIs and keep them in sync — 45 MCP tools with shadow previews and diagnostics.
-
Amazon Trends API
— last commit 2026-08-03, shares ecommerce
Amazon product search volume and best-seller trends. Free key at trendsapi.ai
-
DOOMSCROLLR
— last commit 2026-05-27, shares ecommerce
Build owned-audience websites: pages, posts, products, subscribers, ShopMy/Shopify imports.
-
StoreInspect
— last commit 2026-08-02, shares ecommerce
Search Shopify stores, enrich domains, and reveal approved contact channels.
-
AMZScout Skill + MCP
— last commit 2026-08-06, shares ecommerce
Amazon research from AMZScout data: analyze products & niches, keywords/PPC, and brand catalogs.
-
io.github.auroracapital/claude-ops-telegram-server
— last commit 2026-08-03, shares ecommerce
Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats.
These share tags the maintainers applied themselves, such as headless, ecommerce. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai, assistant, checkout, ecommerce, headless, mcp, mcp-server, swell, swell-mcp.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab