SEOmatic

[SEOmatic]

SEOmatic for AI agents

SEO agent for your own website, in the AI agent you already use. Ask about your real Google Search Console data, audit your pages, check how ChatGPT, Claude, Perplexity and Google AI Overviews describe you, research keywords and backlinks, and stage fixes. Nothing goes live until you approve it; after approval SEOmatic publishes to WordPress, Shopify, Webflow, Wix and other connected CMSs and measures the before and after.

This repository carries every agent's install file in one place: the hosted MCP server config, 21 Agent Skills, Grok Bot templates, and plugin manifests for Claude Code, Cowork, Cursor, Codex, Grok Build, Gemini CLI, Kimi Code and DeepSeek Harness.

A free SEOmatic account (OAuth or API key) can read everything: diagnosis, Search Console, site audits and AI visibility results. Staging fixes over MCP (task_manage create and decide, campaign_manage) needs a paid plan, whose key carries the agents:act scope. Acting through the REST API or CLI needs the Infrastructure plan. Approving always stays with you: an agent only records a decision you made.

Quick start

Add the 21 SEO skills to any agent that reads Agent Skills (Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Kiro and 40+ more):

npx skills add Minh42/seomatic-mcp --full-depth

Then connect the MCP server they use (OAuth, free account, no card):

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

Ask: "Which of my pages are closest to page 1?" The answer cites your real Search Console numbers. Prefer an always-on bot? See the Grok Bot templates.

Contents

• Quick start · What you can ask
• Install: Claude · Claude Cowork · Claude Code · ChatGPT · Codex · Cursor · Grok Bot · Grok Build · Gemini CLI and Gemini · Google Antigravity · Kimi Code · OpenClaw · Hermes Agent · NanoClaw · Paperclip · DeepSeek Harness · Manus and Cue · Perplexity Computer · Muse · OpenCode · Kilo Code · Warp · Goose · Kiro · GitHub Copilot CLI · Cline and other MCP clients · Any agent: skills only
• Skills · Tools · Repository layout · Syncing skills

What you can ask

• Which keywords am I close to ranking on page 1 for?
• Which pages lost traffic in the last 28 days, and why?
• Run a full SEO audit of my site.
• Does ChatGPT mention my site when people ask about my topic?
• What backlinks did I gain this month? Who links to my competitors but not me?
• Write me a weekly SEO brief every Monday.
• How did my local searches move this week, and which reviews need a reply?

Tools are scoped to the workspace you signed in to, so you never pass a domain.

Claude (web and desktop)

Settings, Connectors, Add custom connector:

• Name: SEOmatic
• URL: https://app.seomatic.ai/api/mcp

Click Connect and sign in to SEOmatic. No key needed. For the guided workflows, add the skills under Settings, Capabilities, Skills, Upload skill (zip any folder from skills/).

Claude Cowork

Cowork reads the same plugin as Claude Code. Open Customize, Plugins, Add marketplace, enter Minh42/seomatic-mcp, then install seomatic. It brings the SEOmatic connector (OAuth on first use) and all twenty-one skills. If you only want the connector, add it as in Claude.

Claude Code

As a plugin (MCP server plus twenty-one skills):

/plugin marketplace add Minh42/seomatic-mcp/plugin install seomatic@seomatic

From your shell, the same is claude plugin marketplace add Minh42/seomatic-mcp then claude plugin install seomatic@seomatic. Run /mcp and pick seomatic to sign in.

MCP server only:

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

ChatGPT

ChatGPT web and desktop (plans with developer mode): Settings, Apps and Connectors, Advanced settings, turn on Developer mode, then Create:

• Name: SEOmatic
• MCP server URL: https://app.seomatic.ai/api/mcp
• Authentication: OAuth

Sign in to SEOmatic when ChatGPT asks.

Codex

As a plugin (the repo carries plugin.json, mcp.json and .agents/plugins/marketplace.json in the open plugin format):

codex plugin marketplace add Minh42/seomatic-mcpcodex plugin add seomatic@seomatic

MCP server only:

codex mcp add seomatic --url https://app.seomatic.ai/api/mcpcodex mcp login seomatic

Headless (CI, servers): export SEOMATIC_API_KEY=smk_live_... and codex mcp add seomatic --url https://app.seomatic.ai/api/mcp --bearer-token-env-var SEOMATIC_API_KEY.

Cursor

One click: Add SEOmatic to Cursor

Or add to ~/.cursor/mcp.json:

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

Then Settings, MCP, Connect next to seomatic to sign in. Cursor uses OAuth here: it does not send custom headers to this server, so do not paste an API key into the config.

As a plugin (MCP server, skills and a rule): the repo carries .cursor-plugin/. Install it from the Cursor marketplace once listed, or locally:

git clone https://github.com/Minh42/seomatic-mcp.gitln -s "$(pwd)/seomatic-mcp" ~/.cursor/plugins/local/seomatic

then Developer: Reload Window.

Grok Bot

An always-on SEO teammate on Grok Bot with weekly routines. One click: install SEO Teammate, then connect SEOmatic once (OAuth). Eight more ready-made bots (traffic-drop watch, weekly brief, quick wins, AI visibility, local SEO, agency reports, content planner, technical monitor) install from grok-bot/templates. To build one by hand instead: follow grok-bot/: paste the instructions, connect the MCP server per grok-bot/SETUP.md (OAuth), add the skills and the three routines. For the CLI skill, add SEOMATIC_API_KEY as a bot secret.

Grok Build

The repo carries .grok-plugin/plugin.json (metadata; Grok Build picks up the skills from skills/ and the hosted MCP server, OAuth on first use, from the root .mcp.json) and .grok-plugin/marketplace.json, so Grok Build can add it as a marketplace source: add Minh42/seomatic-mcp as a plugin marketplace, then install seomatic. Once SEOmatic is listed in the xAI plugin marketplace, it installs from there too.

Gemini CLI and Gemini

The repo is a Gemini CLI extension (gemini-extension.json plus GEMINI.md):

gemini extensions install https://github.com/Minh42/seomatic-mcp

It installs the hosted MCP server and the skills. Gemini CLI opens a browser to sign in on first use; run /mcp auth seomatic to sign in again.

MCP server only, in ~/.gemini/settings.json:

{  "mcpServers": {    "seomatic": { "httpUrl": "https://app.seomatic.ai/api/mcp", "oauth": { "enabled": true } }  }}

Gemini CLI was retired for personal Google accounts on 2026-06-18. Google Workspace accounts and Gemini API key users keep it; everyone else can use Google Antigravity.

Gemini web (gemini.google.com) does not take custom MCP servers on personal accounts. Use Gemini CLI, or a Gemini Enterprise workspace where your admin can add https://app.seomatic.ai/api/mcp as a custom MCP connector.

Google Antigravity

Use an API key: Antigravity's OAuth flow for remote MCP servers is broken upstream. Create a key at Settings, AI Agents, then add it from the terminal:

agy mcp add -H "Authorization: Bearer smk_live_YOUR_KEY" seomatic https://app.seomatic.ai/api/mcp

or in ~/.gemini/config/mcp_config.json:

{  "mcpServers": {    "seomatic": {      "serverUrl": "https://app.seomatic.ai/api/mcp",      "headers": { "Authorization": "Bearer smk_live_YOUR_KEY" }    }  }}

Kimi Code

The repo carries kimi.plugin.json (skills plus the MCP server):

/plugins install https://github.com/Minh42/seomatic-mcp

MCP server only:

kimi mcp add --transport http --auth oauth seomatic https://app.seomatic.ai/api/mcpkimi mcp auth seomatic

OpenClaw

Skill from ClawHub (drives the seomatic CLI, needs an API key):

clawhub install @Minh42/seomatic

Then set the key in ~/.openclaw/openclaw.json under skills.entries.seomatic.apiKey, or export SEOMATIC_API_KEY for the gateway. The MCP skills are on ClawHub too (seomatic-seo-audit, seomatic-striking-distance, ...).

MCP server: OpenClaw runs headless, so use an API key. Settings, MCP, Add server:

{  "seomatic": {    "url": "https://app.seomatic.ai/api/mcp",    "transport": "streamable-http",    "headers": { "Authorization": "Bearer smk_live_YOUR_KEY" }  }}

Install in Hermes Agent

The hermes/ folder is a Hermes plugin package (Agent Plugins v1, configuration only): the SEOmatic MCP server plus the twenty MCP skills.

hermes plugins install seomatic --enable

Or straight from this repository, at a commit you choose:

hermes plugins install Minh42/seomatic-mcp/hermes --ref <40-character-commit-sha> --enable

Needs Hermes Agent 0.21.6 or newer and Node.js 20.18.1 or newer with npx. The package runs the pinned [email protected] through npx: on first use it registers an OAuth client named "Hermes Agent (SEOmatic)", opens your browser on the SEOmatic sign-in and a local callback port, and stores the tokens under ~/.mcp-auth. The server is marked untrusted, so Hermes asks before every tool the server does not mark read-only and refuses those in unattended runs.

Before you install, know that:

• every tool call goes to app.seomatic.ai and acts on your own SEOmatic workspace; the tool list comes from the server at runtime;
• Search Console, stored data and the site audit are free; live market data (keyword metrics and suggestions, backlinks, SERP competitors, local SERP visibility), fresh AI visibility scans and approved fixes bill AI credits, and content generation quotes its estimate before it runs;
• fixes proposed through the tools are staged in SEOmatic; approving, publishing, undoing and rolling back change your live site and need your explicit confirmation. SEOmatic's own background agents follow the workspace's autonomy mode (Settings, AI Agents): in Assisted, the default, reversible changes go live on their own with a one-click undo; in Approval every change waits for your yes.

Prefer Hermes's own OAuth client (longer sign-in window) or an API key on a headless machine? Either replaces the package's server and keeps its skills:

hermes mcp add seomatic --url https://app.seomatic.ai/api/mcp --auth oauth

# ~/.hermes/config.yamlmcp_servers:  seomatic:    url: "https://app.seomatic.ai/api/mcp"    headers:      Authorization: "Bearer smk_live_..."

Skills only, without the plugin (all twenty-one, including the CLI skill):

hermes skills tap add Minh42/seomatic-mcp

or one at a time: hermes skills install Minh42/seomatic-mcp/skills/seomatic-seo-audit. The MCP skills declare requires_mcp_servers: [seomatic], so they show up once the server is connected. The seomatic CLI skill asks for SEOMATIC_API_KEY when it loads.

NanoClaw

Keep the key in the OneCLI vault, never in ncl flags. The vault injects it on requests to app.seomatic.ai:

onecli secrets create --name SEOmatic --type api_key \  --value "$SEOMATIC_API_KEY" --host-pattern app.seomatic.ai \  --header-name Authorization --value-format 'Bearer {value}'

Attach that secret to the group's agent (onecli agents set-secrets replaces the whole list, so merge it with the secrets already there), then add the server without any header and restart:

ncl groups config add-mcp-server --id <group-id> --name seomatic \  --url https://app.seomatic.ai/api/mcpncl groups restart --id <group-id>

nanoclaw/add-seomatic-tool.md walks NanoClaw's agent through all of it, including the merge. Copy it into your NanoClaw checkout as .claude/skills/add-seomatic-tool/SKILL.md and run /add-seomatic-tool. It lives outside skills/ so the skills CLI does not install it into other agents. Copy any folder from skills/ into the group's skills to add the guided workflows.

Paperclip

Skills: Skills, Import from GitHub, add Minh42/seomatic-mcp, Find skills, select the SEOmatic skills, Import. Paperclip shows each skill's declared runtime requirements (SEOMATIC_API_KEY for the CLI skill, the seomatic MCP server for the others) on import. Add SEOMATIC_API_KEY as a company secret and expose it to the agents that use SEOmatic. For the MCP skills, add the SEOmatic MCP server to the agent's runtime (for a Claude Code agent: claude mcp add --transport http seomatic https://app.seomatic.ai/api/mcp --header "Authorization: Bearer $SEOMATIC_API_KEY").

DeepSeek Harness (dsh)

The plugins/dsh-seomatic bundle connects dsh to the hosted MCP server and registers a seomatic skill:

dsh plugin --profile web add "github:Minh42/seomatic-mcp#path:/plugins/dsh-seomatic"export SEOMATIC_API_KEY=smk_live_...dsh web

The same bundle is on npm as dsh-seomatic (dsh plugin --profile web add dsh-seomatic). Tools appear as mcp__seomatic__*. Without a key the profile still starts, with no SEOmatic tools. See the plugin README.

Manus and Cue

Settings, Connectors, Custom MCP, Add custom MCP, Direct configuration:

• Name: SEOmatic
• Transport: Streamable HTTP
• URL: https://app.seomatic.ai/api/mcp
• Header: Authorization: Bearer smk_live_YOUR_KEY (or OAuth where offered)

Cue and other agents with a "custom MCP server" screen take the same three values.

Perplexity Computer

Pro, Max and Enterprise: Settings, Connectors, Add custom connector (or perplexity.ai/computer/connectors, + Custom connector):

• Name: SEOmatic
• MCP URL: https://app.seomatic.ai/api/mcp
• Transport: Streamable HTTP
• Authentication: OAuth, or API key with your smk_live_... key

Muse

Ask Muse to add a custom connector for SEOmatic at https://app.seomatic.ai/api/mcp and sign in to SEOmatic when it asks. Use SEOmatic from the connector list instead once it appears there.

OpenCode

In opencode.json (project) or ~/.config/opencode/opencode.json:

{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "seomatic": {      "type": "remote",      "url": "https://app.seomatic.ai/api/mcp",      "headers": { "Authorization": "Bearer smk_live_YOUR_KEY" }    }  }}

Leave out headers to sign in with OAuth instead (opencode mcp auth seomatic).

Kilo Code

kilo.jsonc takes the same block as OpenCode:

{  "mcp": {    "seomatic": {      "type": "remote",      "url": "https://app.seomatic.ai/api/mcp",      "headers": { "Authorization": "Bearer smk_live_YOUR_KEY" }    }  }}

Warp

Settings, AI, MCP servers, + Add, then paste:

{  "seomatic": {    "url": "https://app.seomatic.ai/api/mcp",    "headers": { "Authorization": "Bearer smk_live_YOUR_KEY" }  }}

Goose

goose configure, Add Extension, Remote Extension (Streamable HTTP), name seomatic, URL https://app.seomatic.ai/api/mcp, and an Authorization header of Bearer smk_live_YOUR_KEY. In ~/.config/goose/config.yaml that is:

extensions:  seomatic:    enabled: true    name: seomatic    type: streamable_http    uri: https://app.seomatic.ai/api/mcp    headers:      Authorization: Bearer smk_live_YOUR_KEY    timeout: 300

Kiro

In ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in a project). The Authorization header is the recommended route:

{  "mcpServers": {    "seomatic": {      "url": "https://app.seomatic.ai/api/mcp",      "headers": { "Authorization": "Bearer smk_live_YOUR_KEY" }    }  }}

GitHub Copilot CLI

copilot mcp add --transport http seomatic https://app.seomatic.ai/api/mcp

To use an API key, add the header in ~/.copilot/mcp-config.json:

{  "mcpServers": {    "seomatic": {      "type": "http",      "url": "https://app.seomatic.ai/api/mcp",      "headers": { "Authorization": "Bearer smk_live_YOUR_KEY" },      "tools": ["*"]    }  }}

Cline and other MCP clients

Any client that speaks Streamable HTTP works. With an API key (Cline's cline_mcp_settings.json shown):

{  "mcpServers": {    "seomatic": {      "url": "https://app.seomatic.ai/api/mcp",      "type": "streamableHttp",      "headers": { "Authorization": "Bearer smk_live_YOUR_KEY_HERE" }    }  }}

Clients with OAuth support only need the URL. VS Code and GitHub Copilot find SEOmatic in the GitHub MCP Registry as ai.seomatic/seomatic. The registry entry is published from the SEOmatic app repository's server.json, which is the source; server.json here is a copy kept identical to it. Agents that install MCP servers themselves can follow llms-install.md.

Any agent: skills only

The skills CLI installs into Claude Code, Cursor, Codex, Gemini CLI, OpenClaw and many more:

npx skills add Minh42/seomatic-mcp                # the seomatic CLI skillnpx skills add Minh42/seomatic-mcp --full-depth   # all twenty-one skills

The seomatic skill drives the CLI, so it works in any agent that can run shell commands, with no MCP setup: npx -y seomatic login --device on your own computer, or SEOMATIC_API_KEY on a server.

Skills

Every skill follows the same rules: numbers come from tool results only, date ranges are quoted exactly, and nothing goes live until you approve it.

Tools

Each tool is annotated read-only or staging and scoped to the connected workspace. The main ones: gsc_performance, gsc_insights, gsc_indexing, keyword_research, keyword_clusters, backlink_profile, serp_competitors, site_pages, ai_citations, visibility_manage, traffic_analytics, rank_tracking_read, rank_tracking, business_profile, business_profile_manage, local_presence, dataset_library, strategy_insights, task_manage, campaign_manage. What you see depends on your plan and connected data sources. Reference: https://seomatic.ai/developers/mcp

Repository layout

Syncing skills from the app

Seven MCP skills (approval workflow, AI citations, AI visibility review, local SEO weekly, SEO audit, striking distance, weekly brief) are maintained in the SEOmatic app repository. To refresh them here:

scripts/sync-skills.sh /path/to/seomatic-appgit diff --stat

The script copies skills/seomatic-*/SKILL.md, adds the Paperclip requirements block where the app copy has none, and refreshes the root SKILL.md from skills/seomatic/SKILL.md. A GitHub Action cannot do this without a cross-repo token, so run it by hand before a release. The script overwrites those seven with the app copy, so make kit-only edits to them in the app repo first. It ends by running scripts/build-hermes-skills.sh, which rebuilds hermes/skills/ from skills/; run that by hand after editing any other skill.

License

MIT. Support: https://seomatic.ai/contact