AgentHubAgentHub

SEO Content Machine MCP Setup & Guide

MCP ServerMCP RegistryOfficial

com.seocontentmachine/scm · v1.1.0

Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.

View on MCP Registry ↗Repository ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages. SEO Content Machine is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

secret
Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

Setup tutorial

  1. Open the SEO Content Machine page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add scm -- npx -y seo-content-machine-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for SEO Content Machine

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for SEO Content Machine?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

SEO Content Machine requires environment variables (SCM_API_URL、SCM_API_KEY). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}
Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

SEO Content Machine Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: scmExecute the core tool interface of SEO Content Machine
Request ArgumentsJSON Schema
{
  "target": "SEO Content Machine",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • When your AI Agent needs tool calling capabilities in this domain
  • Automating repetitive workflows in your IDE or terminal
  • Pairing with modern clients supporting MCP/Skill standards
When NOT to Use
  • When missing required API secrets or local runtime prerequisites
  • Pure conversational requests that don't need external system access
Recommended Workflow Pairing:

SEO Content Machine + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like thisSearch similarPick by scenarioPrompt playbooksMCP hands-onReviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: SEO Content Machine
HTML
<a href="https://myagenthub.cn/p/com.seocontentmachine/scm" title="Listed on AgentHub: SEO Content Machine" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/com.seocontentmachine/scm?lang=en" alt="Listed on AgentHub: SEO Content Machine" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: SEO Content Machine](https://myagenthub.cn/badge/com.seocontentmachine/scm?lang=en)](https://myagenthub.cn/p/com.seocontentmachine/scm)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "com.seocontentmachine/scm",
  "type": "mcp-server",
  "version": "1.1.0",
  "displayName": "SEO Content Machine",
  "description": "Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.",
  "repository": {
    "url": "https://github.com/gitTerebi/seo-content-machine-plugin",
    "source": "github",
    "subfolder": "mcp"
  },
  "homepage": "https://seocontentmachine.com",
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "seo-content-machine-mcp",
        "version": "1.1.0",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "SCM_API_URL",
            "description": "SCM API server address. Default http://localhost:8008"
          },
          {
            "name": "SCM_API_KEY",
            "description": "The key from SCM Settings > App > Api secret key, if you set one",
            "isSecret": true
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "com.seocontentmachine/scm",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/com.seocontentmachine%2Fscm/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}