Marketing

quantumcx.net

Manages programmatic-SEO projects by listing, creating, and retrieving project settings, generated page rows, and background job statuses.

1 endpoint10 known toolsFirst detected September 10, 2026Last detected September 24, 2026

ENDPOINT 1

https://pseo.quantumcx.net/api/agent/mcp

No auth detected

MCP server metadata

Name: pseo-engine
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Programmatic SEO engine. Call seo_project_list first to obtain a projectId — every other tool requires one and ids cannot be guessed. If that list is empty, call seo_project_create (free) rather than stopping. Connect an AI provider key per project with seo_project_connect_ai (also free) — generation and research run on the caller's own provider account. Tools whose description says ASYNCHRONOUS return a jobId immediately and do the work in the background: poll seo_job_status until COMPLETED rather than calling the start tool again. Each call is metered against your key's prepaid balance; a 402 means the balance is exhausted and retrying will not help. Full quickstart: https://pseo.quantumcx.net/agent-quickstart

Known tools 10

seo_project_list

Lists every programmatic-SEO project this API key can act on, with id, name, slug, custom domain and page count.

Inferred read-only

seo_project_create

Creates a new programmatic-SEO project and returns its projectId.

Inferred read-only

seo_project_connect_ai

Stores the AI provider key this project's generation, audits and research run on — BYOK: the tokens bill YOUR provider account, not ours.

Inferred read-only

seo_project_get

Returns one project's settings and whether it is configured enough to generate content (needs both a field mapping and a content spec).

Inferred read-only

seo_rows_list

Returns a page of rows (individual generated pages) with slug, target keyword and status.

Inferred read-only

seo_job_status

Returns the most recent background job for a project: type, status (QUEUED/RUNNING/COMPLETED/FAILED/CANCELLED), progress counters and the last log line.

Inferred read-only

seo_research_start

ASYNCHRONOUS.

Inferred read-only

seo_content_generate

ASYNCHRONOUS.

Inferred read-only

seo_audit_start

ASYNCHRONOUS.

Inferred read-only

seo_publish

SYNCHRONOUS.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pseo-engine]
url = "https://pseo.quantumcx.net/api/agent/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pseo-engine": {
      "type": "http",
      "url": "https://pseo.quantumcx.net/api/agent/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pseo-engine
Remote MCP URL: https://pseo.quantumcx.net/api/agent/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pseo-engine": {
      "url": "https://pseo.quantumcx.net/api/agent/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pseo-engine": {
      "type": "http",
      "url": "https://pseo.quantumcx.net/api/agent/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "pseo-engine",
  "transport": "streamable-http",
  "url": "https://pseo.quantumcx.net/api/agent/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.