SEO Content Factory vs Scrivener MCP
A side-by-side look at the SEO Content Factory and Scrivener MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SEO Content FactoryMarketingDraft SEO blog articles from topic to ready-to-review post.36FairAuth: not declaredVerdict: choose SEO Content Factory for marketing work; choose Scrivener MCP for knowledge & memory 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 Factory when
- You need dedicated capabilities in the Marketing domain.
Choose Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SEO Content Factory | |
|---|---|---|
| Category | Marketing | Knowledge & Memory |
| Quality signal | 36/100 · Fair | 61/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 67 |
| Directory activity | 0 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View SEO Content Factory | View Scrivener MCP |
Tools & capabilities
SEO Content Factory tools
No tool names declared yet. Check the project README from the listing page.
Scrivener MCP 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 Factory
No confirmed install command for SEO Content Factory yet — follow the setup steps linked from its listing page rather than a guessed package name.
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
SEO Content Factory is categorized under Marketing and uses an install path we have not confirmed yet. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick SEO Content Factory for marketing work and Scrivener MCP for knowledge & memory.
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 Factory has no confirmed install command yet — follow its own setup instructions.
SEO Content Factory has no declared pricing — check the project's own site. Scrivener MCP is listed as free. Auth: no auth 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-factory and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SEO Content Factory has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.