Seonix

Connect it to your AI

Claude Code

claude mcp add --transport http seonix https://api.seonix.ai/mcp

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://api.seonix.ai/mcp

This server expects extra headers, usually an API key from its maker.

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "seonix": {
      "url": "https://api.seonix.ai/mcp"
    }
  }
}

Tools it offers

41 tools, as the server itself reported during our check on Oct 31, 2026.

• acknowledge_issueMark an issue thread as an intentional choice (write scope — ask the user first): it stops counting against the score and stays marked across scans. Typical uses: noindex on pagination, a deliberately short page, a redir
• analyze_seoRun Seonix's deterministic SEO + readability + AI-answer (AEO) scoring on ANY draft you pass (title + HTML + meta + keyphrase). No AI credits are spent. Use it as a linter: fix the problems it lists, re-run until the sco
• apply_fixHave Seonix apply fixes on the live site through the WordPress plugin (write scope — tell the user exactly which issue codes and get a yes first). Works for get_fix_plan items with fix_tier auto or ai_assist (wp_plugin_f
• get_accountThe Seonix account behind this API key: email, every project with its plan, whether the MCP is available for it (paid plans only), AI/publish permissions and this month's article quota. Call this first.
• get_ai_visibilityThe latest AI Visibility snapshot: how often the brand appears in ChatGPT answers for the project's prompts, which competitors are mentioned, top cited sources. Measurement covers ChatGPT only.
• get_articleOne article with SEO title, meta description, excerpt, key takeaways, the stored SEO analysis, publications (where it is live) and optionally the full HTML.
• get_blog_integration_guideThe Seonix skill for connecting a custom-built site or blog as a publishing channel (endpoints, payload, read routes, media, self-test, hand-over). Same text as https://seonix.ai/SKILL.md. Pass section to get one step.
• get_calendarCalendar slots for a month: planned / writing / completed / failed, kind create or optimize, source manual or autopilot, linked article ids.
• get_clusterOne cluster with its member keywords, the site pages already covering it, the live SERP snapshot status and the competitor insights Seonix extracted (must-mention entities, recommended blocks, topical coverage, gaps).
• get_fix_planAn ordered, implementable plan for every open problem: what to change, where (page / site-wide / theme), on which URLs, with the target example. Returned as structured items; pass include_markdown=true to also get a Mark
• get_fix_runStatus and outcome of an apply_fix run: counts (applied / already correct / no-op / errors) and the per-item results with the before and after values.
• get_issueOne issue with the evidence the scanner captured on the page (the offending tag, heading outline, redirect chain, JSON-LD block…) and the remediation profile: why it matters, bad vs good example, how-to-fix steps, whethe
• get_plan_statusPlan and entitlements for one project: whether the MCP is available, AI generation and publishing permissions, article quota used/limit, and the upgrade link when the project is on Free.
• get_playbookRead one Seonix playbook by name (same text as the prompt of that name) — for clients that do not surface MCP prompts.
• get_projectOne project: site URL, language, autopilot mode and cadence, Search Console connection, publishing channels, plan and quota, SEO progress level, dashboard links. Paid plans only.
• get_remediation_profileThe Seonix remediation profile for an issue code (no project needed): why it matters, bad/good example, fix steps, fix tier, warnings. Use when you meet an unfamiliar code.
• get_resultsProof-of-ranking ledger: for each published article, Search Console clicks / impressions / position now vs the previous period, with trend. Requires Search Console.
• get_scan_statusProgress of one scan: stage, pages found / scanned, counts, whether background probes are still pending. Poll every 5–10 seconds while status is not completed.
• get_seo_progressThe project's SEO Progress ladder: current level and stage, what the next level requires (published articles, quality, Search Console, cluster coverage) and the publishing cadence Seonix recommends for this level.
• get_site_dnaThe project's brand profile Seonix extracted and the owner refined: what the business does, audience, tone, language, writing instructions, topics to avoid — plus the ready-to-use prompt block. Read it before writing or
• get_site_healthSite Health for a project: overall score, the four pillars (SEO, AI search, speed, technical), counts of active / fixed / came-back problems, the top open problems by priority, the last scan and the next scheduled check.
• gsc_coverageIndexing coverage Seonix collected from Search Console: indexed / not indexed / unknown counts, sitemap status, and the pages that are not indexed with Google's verdict.
• gsc_impactSeonix's own impact estimate: current vs potential traffic, keyword coverage, article impacts and top keyword opportunities.
• gsc_opportunitiesKeywords already ranking in a position band (default 4–20) with impressions, ordered by the traffic Seonix estimates they would bring at the target position. The classic striking-distance list: refresh those pages first.
• gsc_page_queriesThe queries one page ranks for (Search Console page+query report filtered to that URL). Use it before rewriting a page's title, meta description or headings.
• gsc_statusWhether Google Search Console is connected for the project, which property, and the last date with published data. Call before other gsc_* tools.
• gsc_timeseriesDaily clicks, impressions, average position and potential traffic for the last N days (7–90), plus the previous-period average position for comparison.
• gsc_top_pagesTop landing pages from Search Console for the window: clicks, impressions, CTR, average position.
• gsc_top_queriesTop search queries from Search Console for the window: clicks, impressions, CTR, average position.
• list_articlesArticles in the project (Seonix-generated and imported): status, scores, keyphrase, cluster, publish dates. Paginated.
• list_channelsConnected publishing channels (WordPress, Ghost, Webflow, Shopify, Wix, Custom API) with status. A project needs a connected channel before anything can be published.
• list_clustersTopic clusters (one target page each) with primary keyword, intent, page type, priority, volume, Search Console impressions and winnability. The content plan is built from these.
• list_issuesPersistent issue threads (one per problem per page) with status open / solved / regressed, filterable by code, URL and status. Paginated. Each item carries the issue id for get_issue.
• list_keyword_candidatesKeywords Seonix researched for the project (seed AI, planner, Search Console, autocomplete, user-added) with volume, competition, Search Console numbers and cluster membership. Paginated; filter by status and substring.
• list_playbooksThe Seonix playbooks (step-by-step procedures that tell you which tools to call): promote a site, work through a page, fix issues in code, keyword map, internal links, write an article, striking distance, monthly report,
• list_projectsProjects (websites) in the account with id, slug, name and site URL. Use the id or slug as project_id in other tools.
• list_scansRecent site scans with status, pages scanned and severity counts.
• rollback_fixReverse the changes an apply_fix run made on the live site, restoring the values the plugin snapshotted before applying (write scope — ask the user first).
• score_articleRe-run the SEO + readability scoring on an article already in Seonix (no changes saved) and list its problems.
• start_scanStart a fresh Site Health scan of the project's site (write scope — ask the user first). Returns the scan id; poll get_scan_status every 10 seconds until status is completed, then call get_site_health / get_fix_plan to s

Questions