pSEO Engine

net.quantumcxPublished by quantumcx.netOfficial publisherv1.0.0Updated Oct 25, 2026

Programmatic SEO as callable tools: research, generate, audit and publish landing pages.

Overview

AI-generated overview

A remote MCP server for programmatic SEO: an assistant can research keywords, generate landing pages, audit them and publish approved pages in a project.

What you can do
List and create programmatic-SEO projects, and inspect a project's settings and readiness to generate content, including connecting the AI provider keys it runs on. Start keyword research that mines and qualifies keywords into pending page rows, and list those rows with slug, keyword and status. Start content generation over pending rows and check the progress of background jobs. Audit generated pages for broken text, unfilled placeholders, truncated copy and missing images. Publish pages that have been approved.
When to use it
Useful when you run a programmatic-SEO site and want an assistant to drive the pipeline end to end: set up a project, research keywords, draft pages, check them and push approved ones live. It suits bulk landing-page production rather than editing a single page by hand.
Requirements
A remote endpoint reached over streamable HTTP, with an agent API key sent in the X-Agent-API-Key header; keys are created after signing up on the provider's site. Each project also needs its own AI provider key stored through the connect tool, and optionally a Perplexity key for citation features.
Before you install
The agent API key is a secret sent in a header. AI provider keys are stored on the service and billed to your own provider account, so generation and research spend real budget. Audits cost 30c per call. Publishing changes live pages, and only rows in reviewed status are published; drafts are skipped. Generated content is sent to third-party AI providers.

Installation

In SourceWeft

  1. Open pSEO Engine in the dashboard and add it to a workspace.
  2. Connect X-Agent-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.quantumcx%2Fpseo-engine/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pseo-engine": {
      "type": "http",
      "url": "https://pseo.quantumcx.net/api/agent/mcp",
      "headers": {
        "X-Agent-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

10

seo_project_list

List projects

Lists every programmatic-SEO project this API key can act on, with id, name, slug, custom domain and page count. Call this FIRST in any session — every other tool needs a projectId from here, and ids cannot be guessed or carried over from another account. FREE — this call costs nothing.

Takes no parameters.

seo_project_create

Create a project

Creates a new programmatic-SEO project and returns its projectId. Call this when seo_project_list comes back empty — every other tool needs a projectId and a new account has none. The project is created EMPTY: it still needs a data source and a content spec before seo_content_generate will run, so call seo_project_get afterwards and read readinessNote. FREE — this call costs nothing.

ParametersnamerequireddomainaiModelaiApiKeytemplateaiBaseUrlperplexityApiKey

seo_project_connect_ai

Connect (or replace) a project's AI keys

Stores the AI provider key this project's generation, audits and research run on — BYOK: the tokens bill YOUR provider account, not ours. Recommended: a Google Gemini API key (aistudio.google.com/apikey); its free tier works with no card. Optionally stores a Perplexity API key to enable citation-bearing AI visibility checks. Keys are stored encrypted and can never be read back — only replaced or cleared. FREE — this call costs nothing.

ParametersaiModelaiApiKeyaiBaseUrlprojectIdrequiredclearAiKeyperplexityApiKeyclearPerplexityKey

seo_project_get

Get one project's configuration and readiness

Returns one project's settings and whether it is configured enough to generate content (needs both a field mapping and a content spec). Use this before seo_content_generate to avoid starting a run that will immediately fail. FREE — this call costs nothing.

ParametersprojectIdrequired

seo_rows_list

List pages in a project

Returns a page of rows (individual generated pages) with slug, target keyword and status. Statuses are PENDING (no content yet), GENERATING, GENERATED (draft), REVIEWED (approved), PUBLISHED (live), FAILED, FLAGGED_DUPLICATE. Content bodies are NOT included — this is a listing, not an export. Use sort:'risk' to get the review queue ordered by risk score (duplicates and pages with QA findings first) so a human reviews the riskiest pages before bulk-approving the safe ones. Costs 3c per call.

ParameterssortlimitstatusprojectIdrequired

seo_job_status

Check the latest background job

Returns the most recent background job for a project: type, status (QUEUED/RUNNING/COMPLETED/FAILED/CANCELLED), progress counters and the last log line. Poll this every few seconds after any tool that starts a job. Do NOT re-call the start tool while status is RUNNING; it will be refused. FREE — this call costs nothing.

ParametersprojectIdrequired

seo_research_start

Start AI keyword research

ASYNCHRONOUS. Starts a keyword-research run that mines and qualifies keywords into PENDING rows. It spends real AI budget, so call it once and then poll seo_job_status until status is COMPLETED. Returns immediately with a jobId — the keywords do NOT exist yet when this returns. Fails if a research run is already in progress. HUMAN trial accounts get one research run free; a second run returns code card_required — only a human on the account can start a plan, so stop and report instead of retrying. Costs 750c per call.

ParametersbriefrequiredprojectIdrequiredtargetCount

seo_content_generate

Generate page content for pending rows

ASYNCHRONOUS. Starts the content-generation queue over every PENDING row in the project. It also spends real AI budget per generated page. Requires the project to be configured (check readyToGenerate via seo_project_get first). Returns a jobId immediately; poll seo_job_status. Generated pages land in GENERATED status and are NOT live until approved and published. Costs 75c per call.

ParametersprojectIdrequired

seo_audit_start

Audit every generated page for defects

ASYNCHRONOUS. Scans all generated pages for broken text, unfilled placeholders, truncated copy and missing images, recording findings per page. Returns a jobId; poll seo_job_status. This only REPORTS problems — it does not fix them. Costs 30c per call.

ParametersprojectIdrequired

seo_publish

Publish approved pages

SYNCHRONOUS. Takes approved pages live. IMPORTANT: only rows in REVIEWED status are published — GENERATED drafts are deliberately skipped, because approval is a human gate in this product. The response reports how many were skipped and why; if publishedCount is 0 and skippedNeedsReview is high, the pages need approving in the dashboard first. Costs 15c per call.

ParametersprojectIdrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.