Contentforge runs on your own machine — the client starts it, so there is no endpoint to ping. 33 installs a week from npm.
Content pipeline MCP server — image sourcing, SEO, affiliate links, and CMS publishing.
The linked repository no longer exists on GitHub — it was deleted or made private.
We have not read this server's code yet
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
contentforge-mcp похож на contextforge-mcp
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Contentforge and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add contentforge -e 'CONTENTFORGE_CMS_URL=<CONTENTFORGE_CMS_URL>' -e 'CONTENTFORGE_CMS_KEY=<CONTENTFORGE_CMS_KEY>' -- npx -y contentforge-mcp
{
"mcpServers": {
"contentforge": {
"command": "npx",
"args": [
"-y",
"contentforge-mcp"
],
"env": {
"CONTENTFORGE_CMS_KEY": "<CONTENTFORGE_CMS_KEY>",
"CONTENTFORGE_CMS_URL": "<CONTENTFORGE_CMS_URL>"
}
}
}
}
[mcp_servers.contentforge]
command = "npx"
args = ["-y", "contentforge-mcp"]
env = { CONTENTFORGE_CMS_URL = "<CONTENTFORGE_CMS_URL>", CONTENTFORGE_CMS_KEY = "<CONTENTFORGE_CMS_KEY>" }
{
"mcpServers": {
"contentforge": {
"command": "npx",
"args": [
"-y",
"contentforge-mcp"
],
"env": {
"CONTENTFORGE_CMS_KEY": "<CONTENTFORGE_CMS_KEY>",
"CONTENTFORGE_CMS_URL": "<CONTENTFORGE_CMS_URL>"
}
}
}
}
{
"servers": {
"contentforge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"contentforge-mcp"
],
"env": {
"CONTENTFORGE_CMS_KEY": "<CONTENTFORGE_CMS_KEY>",
"CONTENTFORGE_CMS_URL": "<CONTENTFORGE_CMS_URL>"
}
}
}
}
Put your own values in place of
<CONTENTFORGE_CMS_URL> (URL of your CMS API endpoint), <CONTENTFORGE_CMS_KEY> (API key for your CMS).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
CONTENTFORGE_PEXELS_KEY (Pexels API key for image sourcing), CONTENTFORGE_AMAZON_TAG (Amazon Associates affiliate tag).
Strapi CMS MCP — natural-language content management: create, manage, and publish content.
PostKing MCP server for managing brands, generating posts, scheduling content, and publishing blogs.
Publish, search, and manage Xiaohongshu (Little Red Book) content via MCP tools.
Agent-first SEO research and publishing: competitors, SERPs, internal links, and Search Console.
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
Sling CLI MCP server for data pipeline and replication management
WordPress MCP server: publish posts, AI images, SEO and full site management, self-hosted
Answers built from our own checks of this server.