MarketCore vs Topicforge MCP
A side-by-side look at the MarketCore and Topicforge MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MarketCoreMarketingCreate on-brand marketing deliverables and GTM docs with AI-powered blueprints and brand guidelines.38FairAuth: not declaredVerdict: choose MarketCore for marketing work; choose Topicforge MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Topicforge MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TOPICFORGE_API_KEY, CONTENT_API_BASE_URI. - You want tools like
topic_cluster, faq_schema, meta_description.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MarketCore | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 38/100 · Fair | 55/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | TOPICFORGE_API_KEYCONTENT_API_BASE_URI |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View MarketCore | View Topicforge MCP |
Tools & capabilities
MarketCore tools
No tool names declared yet. Check the project README from the listing page.
Topicforge MCP tools 9
topic_clusterExpand a seed topic into 15–25 article ideasfaq_schemaFAQ questions + FAQPage JSON-LDmeta_description150–160 char meta descriptionrun_batchLaunch a credit-debited batch job (pay per article)get_batch_statusPoll batch job progressget_articleFetch article by IDexport_markdownExport article as markdownget_generation_settingsRead workspace voice profile, product facts, and effective settingsupdate_generation_settingsUpdate workspace generation settings used by `run_batch
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.
MarketCore
No confirmed install command for MarketCore yet — follow the setup steps linked from its listing page rather than a guessed package name.
Topicforge MCP
{
"mcpServers": {
"topicforge-topicforge-mcp": {
"command": "npx",
"args": [
"-y",
"@topicforge/mcp"
],
"env": {
"TOPICFORGE_API_KEY": "YOUR_TOPICFORGE_API_KEY_HERE",
"CONTENT_API_BASE_URI": "YOUR_CONTENT_API_BASE_URI_HERE"
}
}
}
}
Frequently asked questions
MarketCore is categorized under Marketing and uses an install path we have not confirmed yet. Topicforge MCP belongs to Marketing and uses a local stdio subprocess. Pick MarketCore for marketing work and Topicforge MCP for marketing.
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. MarketCore has no confirmed install command yet — follow its own setup instructions.
MarketCore has no declared pricing — check the project's own site. Topicforge MCP is listed as a paid service. 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 marketcore and topicforge-topicforge-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MarketCore has a quality signal of 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Topicforge MCP has 55/100 (Good) with 3 views, 0 installs and 0 GitHub stars.