SEO Content Machine vs Amazon Scraper API
A side-by-side look at the SEO Content Machine and Amazon Scraper API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SEO Content MachineSearch & Data Extraction · Remote HTTP/SSERun SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.40FairAuth: not declared
Amazon Scraper APISearch & Data Extraction · Local subprocess (stdio)Scrape Amazon products, search, and async batch ASIN lookups across 20 marketplaces51GoodAuth: not declaredVerdict: choose SEO Content Machine for search & data extraction work over a hosted endpoint; choose Amazon Scraper API for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose SEO Content Machine when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
Choose Amazon Scraper API when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ASA_API_KEY. - You want tools like
amazon_product, amazon_search, amazon_batch_create.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SEO Content Machine | Amazon Scraper API |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 40/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ASA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View SEO Content Machine | View Amazon Scraper API |
Tools & capabilities
SEO Content Machine tools
No tool names declared yet. Check the project README from the listing page.
Amazon Scraper API tools 4
amazon_productFetch one product by ASIN or URLamazon_searchKeyword search with sort/filteramazon_batch_createQueue up to 1000 ASINs for async scrapeamazon_batch_statusPoll a batch's progress
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SEO Content Machine
{
"mcpServers": {
"seo-content-machine": {
"url": "http://localhost:8008/mcp"
}
}
}
Amazon Scraper API
{
"mcpServers": {
"amazon-scraper-api": {
"command": "npx",
"args": [
"-y",
"amazon-scraper-api-mcp"
],
"env": {
"ASA_API_KEY": "YOUR_ASA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
SEO Content Machine is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Amazon Scraper API belongs to Search & Data Extraction and uses a local stdio subprocess. Pick SEO Content Machine for search & data extraction work and Amazon Scraper API for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SEO Content Machine has no declared pricing — check the project's own site. Amazon Scraper API has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add seo-content-machine and amazon-scraper-api as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SEO Content Machine has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Amazon Scraper API has 51/100 (Good) with 1 views, 0 installs and 2 GitHub stars.