# Seonix MCP server

> Read Site Health, fix plans, Search Console data, keywords and article scores from your Seonix SEO account.

- Listing: https://mcp.tc/i/seonix
- Connect: use the server's own URL `https://api.seonix.ai/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo)
- Vendor: Seonix
- Homepage: <https://seonix.ai/mcp>

## About

Seonix connects an AI agent to a Seonix account, an SEO engine that crawls your site, tracks issues across scans and reads Google Search Console. The agent can pull the Site Health report, get an ordered fix plan, browse keyword clusters and articles, and score drafts before publishing. A few write tools can start scans or apply and roll back fixes through the WordPress plugin.

It runs as a hosted Streamable HTTP endpoint at https://api.seonix.ai/mcp. Access needs a personal Seonix bearer key sent in a header, obtained through a device flow in the agent. OAuth sign-in for Claude.ai and ChatGPT connectors is not available yet. The MCP is included in paid plans.

## What it can do

- Read Site Health scores and open issues with page evidence
- Get an ordered fix plan for code or site changes
- Query Search Console top queries, pages and striking-distance keywords
- Browse keyword candidates, clusters and articles
- Score drafts for SEO, readability and AI-answer quality
- Start scans and apply or roll back WordPress fixes with user approval
- Follow built-in SEO playbooks

## Tools (41)

- `acknowledge_issue`: Mark an issue as intentional so it stops counting (write scope).
- `analyze_seo`: Score any draft for SEO, readability and AI-answer quality. (read-only)
- `apply_fix`: Apply fixes on the live site via the WordPress plugin (write scope). (can modify or delete data)
- `get_account`: Account overview with projects, plan and article quota; call first. (read-only)
- `get_ai_visibility`: How often the brand appears in ChatGPT answers. (read-only)
- `get_article`: One article with SEO fields, analysis and publications. (read-only)
- `get_blog_integration_guide`: Guide for connecting a custom blog as a publishing channel. (read-only)
- `get_calendar`: Content calendar slots for a month. (read-only)
- `get_cluster`: One cluster with keywords, covering pages and competitor insights. (read-only)
- `get_fix_plan`: Ordered, implementable plan for every open problem. (read-only)
- `get_fix_run`: Status and per-item results of an apply\_fix run. (read-only)
- `get_issue`: One issue with captured page evidence and remediation profile. (read-only)
- `get_plan_status`: Plan entitlements and quota for a project. (read-only)
- `get_playbook`: Read one Seonix playbook by name (same text as the prompt of that name) — for clients that do not surface MCP prompts. (read-only)
- `get_project`: One project's details, channels, plan and progress. (read-only)
- `get_remediation_profile`: Why an issue code matters and how to fix it. (read-only)
- `get_results`: Search Console performance ledger for published articles. (read-only)
- `get_scan_status`: Progress of a single scan. (read-only)
- `get_seo_progress`: SEO progress level and next-level requirements. (read-only)
- `get_site_dna`: Brand profile and writing instructions for the site. (read-only)
- `get_site_health`: Overall score, four pillars, issue counts and top open problems. (read-only)
- `gsc_coverage`: Indexing coverage and non-indexed pages. (read-only)
- `gsc_impact`: Seonix impact estimate with keyword opportunities. (read-only)
- `gsc_opportunities`: Keywords ranking in a position band, ordered by estimated traffic gain. (read-only)
- `gsc_page_queries`: Queries a specific page ranks for. (read-only)
- `gsc_status`: Whether Search Console is connected and the latest data date. (read-only)
- `gsc_timeseries`: Daily clicks, impressions and position over 7 to 90 days. (read-only)
- `gsc_top_pages`: Top landing pages from Search Console. (read-only)
- `gsc_top_queries`: Top Search Console queries with clicks, impressions, CTR and position. (read-only)
- `list_articles`: Articles with status, scores and publish dates. (read-only)
- `list_channels`: Connected publishing channels and their status. (read-only)
- `list_clusters`: Topic clusters with intent, page type and priority. (read-only)
- `list_issues`: Persistent issue threads filterable by code, URL and status. (read-only)
- `list_keyword_candidates`: Researched keywords with volume, competition and cluster membership. (read-only)
- `list_playbooks`: List the available SEO playbooks. (read-only)
- `list_projects`: Projects in the account with ids and slugs. (read-only)
- `list_scans`: Recent site scans with status and severity counts. (read-only)
- `rollback_fix`: Reverse the changes made by an apply\_fix run (write scope). (can modify or delete data)
- `score_article`: Re-score an existing article and list its problems. (read-only)
- `start_scan`: Start a new Site Health scan (write scope).
- `unacknowledge_issue`: Remove the intentional mark from an issue.

## Example prompts

- "Get my Site Health and list the top open problems"
- "Build a fix plan and apply the page-level items in this repo"
- "Show striking-distance keywords from Search Console for the last 28 days"
- "Score this draft article and tell me what to fix before publishing"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

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

2. Start Claude Code and type `/mcp`. **seonix** should show as connected.

Seonix needs an API key. Seonix’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Claude Desktop

1. Use the `mcp-remote` bridge, which keeps the key on this computer (a connector added on claude.ai with the key under **Request headers** also shows up here). Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "seonix": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.seonix.ai/mcp"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=seonix&config=eyJ1cmwiOiJodHRwczovL2FwaS5zZW9uaXguYWkvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

Seonix needs an API key. Seonix’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=seonix&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.seonix.ai%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"seonix","type":"http","url":"https://api.seonix.ai/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "seonix": {
      "type": "http",
      "url": "https://api.seonix.ai/mcp"
    }
  }
}
```

Seonix needs an API key. Seonix’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "seonix": {
      "serverUrl": "https://api.seonix.ai/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add seonix --url https://api.seonix.ai/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.seonix]
url = "https://api.seonix.ai/mcp"
```

Seonix needs an API key. Seonix’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Gemini CLI

```bash
gemini mcp add --transport http seonix https://api.seonix.ai/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "seonix": {
      "type": "http",
      "url": "https://api.seonix.ai/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.seonix.ai/mcp`.

Seonix needs an API key. Seonix’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

## Recent changes

- 2026-10-29 23:46 UTC: 1 tool changed. Source: automatic check. Changed: get\_site\_dna.
- 2026-10-27 11:38 UTC: Tracking started: 41 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/seonix#history (Atom feed: https://mcp.tc/i/seonix/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.1.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-27
- Updated: 2026-10-29

---
Source: https://mcp.tc/i/seonix (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
