Seonix MCP

What Seonix MCP does

Seonix MCP provides an MCP interface to a Seonix SEO project. Agents can inspect the project account, plan entitlements, site configuration, scan results, SEO progress, brand profile, content calendar, articles, keyword clusters, and remediation guidance.

The server is suited to SEO workflows that need structured evidence rather than a general web search. Site Health reports summarize SEO, AI search, speed, and technical pillars. Individual issues can include captured page evidence such as tags, heading structure, redirects, or JSON-LD, along with examples and repair instructions.

Search Console tools cover connection status, indexing coverage, pages, queries, time series, traffic opportunities, and estimated impact. Content tools support article listings, article details, draft scoring, keyphrase analysis, and cluster-level coverage. AI visibility reporting focuses on how often a brand appears in ChatGPT answers for the project's prompts.

How it works

The service is available at https://api.seonix.ai/mcp over remote Streamable HTTP. Authentication uses a Bearer key obtained through Seonix's one-click device flow. After connecting, call get_account to identify the account, projects, plan access, permissions, and article quota. Project-specific tools use the relevant project context and paid-plan availability where required.

For a site diagnosis, start with get_site_health, then inspect open problems with get_issue or build an ordered remediation list with get_fix_plan. Long-running scans expose progress through get_scan_status; poll that tool every 5–10 seconds until completion. After an approved WordPress fix run, use get_fix_run and then start a scan before checking Site Health again.

Draft analysis is independent of publishing. analyze_seo accepts a title, HTML, meta description, and keyphrase, then returns deterministic SEO, readability, and AI-answer scoring without spending AI credits. The result can be used as a linter and rerun after edits.

Setup and configuration

Configure an MCP client with the remote endpoint and a Bearer credential created through Seonix's device flow. The connected Seonix account must have access to the target project; MCP availability and capabilities depend on the project's plan and permissions.

Google Search Console tools require a connected Search Console property. WordPress-based fixes require a connected WordPress channel. Custom-built sites or blogs can use get_blog_integration_guide for the publishing-channel endpoints, payloads, read routes, media handling, self-test, and handover steps.

Tools and capabilities

• Inspect account, project, plan, quota, permissions, autopilot settings, publishing channels, and SEO progress.
• Read Site Health scores, scan state, issue evidence, remediation profiles, fix plans, and fix-run outcomes.
• Query Search Console status, indexing coverage, page queries, top pages, top queries, time series, and ranking opportunities.
• Review keyword clusters, member terms, covered pages, SERP snapshots, competitors, entities, content gaps, and recommended blocks.
• List articles and retrieve stored analyses, publication details, HTML, scores, keyphrases, and cluster assignments.
• Read site DNA, playbooks, calendar entries, AI visibility snapshots, and ranking-result ledgers.
• Score arbitrary drafts with SEO, readability, and AEO checks.
• Acknowledge or unacknowledge issues and apply eligible fixes through a connected WordPress plugin after user confirmation.