
SEO Content Machine
com.seocontentmachinev1.1.0Updated Sep 30, 2026
Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.
Installation
In SourceWeft
- Open SEO Content Machine in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
SEO Content Machine MCP server
Connects Claude Code, Codex, Claude Desktop or any MCP client to SEO Content Machine (SCM), the desktop SEO workspace.
Your assistant can then create and run SCM tasks and read their results: article scraping from search results, site crawls, Google Maps listings, archive.org downloads and SEO Workspace pages. The work runs inside the SCM app on your machine, with its own browser and task queue.
Requirements
- SEO Content Machine running on the same machine, on Windows, Mac or Linux. There is a 14-day free trial, no card needed.
- Node.js 18 or newer.
Setup
Claude Code:
Any other MCP client, in its config file:
If you set an API key in SCM (Settings > App > Api secret key), pass it as SCM_API_KEY. If SCM's API runs somewhere other than http://localhost:8008, set SCM_API_URL.
Tools
How it works
SCM serves MCP over HTTP at /mcp inside the app. This package is a small stdio relay: the client talks to it over stdin and stdout, and it forwards each message to the app. You can start SCM before or after your MCP client. While SCM is closed the server lists no tools, and it tells the client to list them again once SCM starts. Tool calls made while SCM is closed return an error that says to start it.
Source: mcp/README.md at commit b6b1137
Tools
0Version history
1- v1.1.0LatestSep 30, 2026
