SEO Content Machine
LocalAbout SEO Content Machine
SEO Content Machine MCP server connects MCP clients to the SEO Content Machine desktop workspace. It lets assistants run content, research, crawling and workspace tasks in the app and inspect their results.
Key features
- 01Run and manage SCM tasks
- 02Scrape articles from search results
- 03Crawl sites and find URLs
- 04Collect Google Maps listings and YouTube subtitles
- 05Read and update SEO Workspace content
- 06Search, browse pages and render PDFs
Use cases
- 01Run keyword-based page pipelines
- 02Extract rendered page data into CSV
- 03Collect archived pages for a domain
- 04Read or revise SEO Workspace documents
MCP support
SCM exposes MCP over HTTP inside the desktop app; this package relays stdio client messages to it. Clients can call task, scraping, browser and workspace tools.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y seo-content-machine-mcpSCM_API_URLSCM API server address. Default http://localhost:8008SCM_API_KEYSecretThe key from SCM Settings > App > Api secret key, if you set oneLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMESEO 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, search result lists, Google Maps listings, YouTube subtitles, 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:
claude mcp add scm -- npx -y seo-content-machine-mcp
Any other MCP client, in its config file:
{
"mcpServers": {
"scm": {
"command": "npx",
"args": ["-y", "seo-content-machine-mcp"]
}
}
}
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
| Tool | What it does |
|---|---|
task_list, task_get, task_results | List SCM tasks, read one with its log, read the result rows of its last run, which point to its output files |
task_run, task_cancel, task_delete | Start (or start over with fromStart), stop or delete a task |
page_pipeline_upsert | Create or change a Page Pipeline: AI pages from page templates, or articles scraped from search results, for a list of keywords |
dynamic_pages_create | Extract values from rendered pages into CSV with CSS selectors |
static_pages_create | Fetch pages without a browser and save each as a cleaned article |
site_crawler_create | Crawl a site and save the links it finds |
url_finder_create | Search a list of queries and save every result to one CSV of query, rank, url and title |
youtube_subtitles_create | Save the subtitles of YouTube videos, from video URLs or keyword searches |
web_archives_create | Download the newest archive.org copy of each page on a domain |
local_listings_create | Scrape Google Maps listings, such as "plumbers in denver" |
seo_workspace_create | Create an empty SEO Workspace |
workspace_query | Read an SEO Workspace: its pages, site plan, brief, documents, crawl and Search Console data |
workspace_write | Add or update pages, the site plan, the brief or documents in an SEO Workspace, with undo in the app |
workspace_create_pages | Hand SEO Workspace pages to a Page Pipeline, which researches, writes and reviews each one as a draft |
workspace_documents_edit | Replace exact text in one SEO Workspace document |
web_search, browser_open, cdp_open | Search the web, read a page, or drive a real browser |
render_pdf | Print an HTML document to a PDF file |
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.