SEO Content Machine vs Lilbee
A side-by-side look at the SEO Content Machine and Lilbee 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 declaredVerdict: choose SEO Content Machine for search & data extraction work over a hosted endpoint; choose Lilbee 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 Lilbee when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SEO Content Machine | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 40/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 63 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View SEO Content Machine | View Lilbee |
Tools & capabilities
SEO Content Machine tools
No tool names declared yet. Check the project README from the listing page.
Lilbee tools
No tool names declared yet. Check the project README from the listing page.
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"
}
}
}
Lilbee
{
"mcpServers": {
"tobocop2-lilbee": {
"command": "npx",
"args": [
"-y",
"lilbee"
]
}
}
}
Frequently asked questions
SEO Content Machine is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Lilbee belongs to Search & Data Extraction and uses a local stdio subprocess. Pick SEO Content Machine for search & data extraction work and Lilbee 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. Lilbee is listed as free. Auth: api key required. 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 tobocop2-lilbee 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. Lilbee has 59/100 (Good) with 1 views, 0 installs and 63 GitHub stars.