Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.
Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y seo-content-machine-mcp
MCP client config
{
"mcpServers": {
"seo-content-machine": {
"command": "npx",
"args": [
"-y",
"seo-content-machine-mcp"
]
}
}
}Lets Claude Code drive SEO Content Machine (SCM), the desktop SEO workspace. Claude can create and run SCM tasks and read their results:
The plugin adds SCM's MCP server and a skill that shows Claude how to use it.
In Claude Code:
/plugin marketplace add gitTerebi/seo-content-machine-plugin
/plugin install seo-content-machine@seo-content-machine
The plugin works with SCM's default settings. It has two optional settings, which you can change in /config:
http://localhost:8008.You can open SCM before or after Claude Code. The SCM tools appear once SCM is running.
Open SCM, then ask Claude Code for the job, for example:
The MCP server is one file, mcp/index.mjs, with no dependencies. Claude Code runs it with Node. It reads messages from Claude Code on stdin and posts each one to SCM's API at the SCM API address, http://localhost:8008/mcp by default, with the API key as a Bearer header when you set one. It sends nothing anywhere else.
While SCM is closed, the server checks that address every 5 seconds and tells Claude Code to list the tools again once SCM answers.
The work itself runs inside SCM on your machine. Tasks you start through it browse and scrape the sites and searches you ask for, and write their results to SCM's output folders.
The same server is on npm as seo-content-machine-mcp for other MCP clients.
MIT