Use SEOmatic in Kilo Code
Updated
Before you start
Kilo Code in VS Code, a JetBrains IDE or the CLI, and a free SEOmatic account. For CI or a machine with no browser, create an API key in Settings, AI Agents, API Keys.
Connect Kilo Code#
- Open Kilo's MCP config. Open ~/.config/kilo/kilo.jsonc (or .kilo/kilo.jsonc in one repo). In the terminal you can run kilo mcp add instead. In VS Code, Kilo's docs also list Settings, Agent Behaviour, MCP Servers, Add Server, Remote (HTTP).
- Add the seomatic server. Name it seomatic with the URL https://app.seomatic.ai/api/mcp. In kilo.jsonc, that is an entry under mcp with "type": "remote". Keep any servers already there.
- Sign in to SEOmatic. Kilo opens the SEOmatic sign-in in your browser when it connects. If it does not, run kilo mcp auth seomatic. Sign in or create a free account, approve access and pick your site.
- Allow the tools. Kilo asks before each SEOmatic tool the first time. Click Approve Always in VS Code to save an allow rule, or add "seomatic_*": "allow" under permission in kilo.jsonc.
- Check the connection. In VS Code, open Settings, Agent Behaviour, MCP Servers and check that seomatic is turned on. In the CLI, run kilo mcp list, or /mcps inside a session, and check that seomatic is on.
- Ask about your site. Ask: “How did my site do on Google over the last 28 days?” The answer should name the date range and your real numbers.
Kilo Code setup
// ~/.config/kilo/kilo.jsonc (or .kilo/kilo.jsonc in one repo)
{
"mcp": {
"seomatic": {
"type": "remote",
"url": "https://app.seomatic.ai/api/mcp"
}
}
}
// or, from a terminal:
kilo mcp add
kilo mcp auth seomatic
kilo mcp list
// skip the per-tool prompts
"permission": {
"seomatic_*": "allow"
}
// CI or no browser: add an API key header instead
"seomatic": {
"type": "remote",
"url": "https://app.seomatic.ai/api/mcp",
"headers": {
"Authorization": "Bearer smk_live_..."
}
}Note
A project file (.kilo/kilo.jsonc) wins over the global one, and the CLI also reads a legacy opencode.jsonc, so check those if Kilo seems to ignore a change. Do not commit an API key to a shared repo: keep keys in the global file. Kilo's MCP tools follow its permission system (allow, ask, deny) under the name seomatic_
kilo.jsonc, Kilo Mcp Add, Settings Screen or Skills?
| Route | Best for | How |
|---|---|---|
| kilo.jsonc | Most people: VS Code, the CLI, or a setup you want in the repo | Add the block above to ~/.config/kilo/kilo.jsonc or .kilo/kilo.jsonc. For CI, add an Authorization: Bearer smk_live_... header. |
| kilo mcp add | Terminal users who prefer a guided prompt | Run kilo mcp add, pick a remote server, name it seomatic and paste https://app.seomatic.ai/api/mcp. kilo mcp auth seomatic starts the sign-in if it did not open; kilo mcp list shows the status. |
| Settings, Agent Behaviour, MCP Servers | VS Code users who prefer a form to a file | Kilo's docs list Add Server, then Remote (HTTP), name it seomatic, paste https://app.seomatic.ai/api/mcp, then finish the sign-in. If your build has no Add Server button, use kilo.jsonc or ask the Kilo agent to add the entry. |
| Skills only | Running SEO checks through the SEOmatic CLI | npx skills add Minh42/seomatic-mcp -a kilo, with SEOMATIC_API_KEY set. |
Pick kilo.jsonc in your home folder. One entry reaches Kilo in VS Code and the CLI, and the sign-in starts by itself. Use kilo mcp add if you live in the terminal, or the Settings form if you only use VS Code and want to skip the file.
Try Asking#
- “Which of our pages are close to page one, and what would move them up?”
- “Write a 30-day SEO plan from our Search Console data, then fix the first item.”
- “List the pages Google has not indexed and find the cause in this repo.”
- “Which pages get impressions but few clicks? Rewrite their titles.”
- “Audit the site before I deploy and fix anything that would hurt rankings.”
- “Which questions do AI assistants answer without citing us?”
What It Costs#
Connecting is free. Reading your own data never uses credits: Search Console performance and insights, index status, rankings, site audits, AI citations, traffic and your tasks. Only live market lookups (keyword metrics, search results, backlinks), AI visibility scans and the fixes you approve use AI credits; every tool is labelled free or billed. On the Free plan, market lookups count against 5 free questions a month. The workspace Owner sees every credit spent, by feature, in Settings > Usage. Kilo Code itself is billed by its maker, not by SEOmatic: nothing on our side counts tokens.
Nothing Changes on Your Site Without Your Approval#
Kilo Code works in two places, and both keep you in charge. In your repo, it edits files and you review the diff before anything ships. In your CMS, it can only stage a fix in SEOmatic. A staged change is a proposal: it says what will change and why, and nothing touches your site until you approve it. The assistant records your decision, and it is told never to approve anything on its own judgment. Approved fixes start within seconds, the page's previous state is stored, and any applied change can be rolled back. Changes that could take a page out of Google, like a noindex, need an extra explicit confirmation.
- Kilo Code says SEOmatic is connected but answers without my data.
- Start a new chat and check that SEOmatic is enabled for that conversation in the tools menu. This is the step most people miss.
- The SEOmatic page says "This connection request expired".
- Start the connection again from Kilo Code, or paste the setup prompt again.
- The Authorize page shows the wrong email or no workspace.
- Click Switch account on that page and sign in with the SEOmatic account that owns the site.
- Why does Kilo Code say it cannot change my site?
- Fixes need a live paid plan or trial. On the Free plan, or when billing is paused or failed, your assistant can read and answer only.
- How do I disconnect?
- Open Settings > AI Agents, scroll to API Keys and delete the row named OAuth: Kilo Code. See disconnect an assistant.
Was This Article Helpful?
Still need help?Email contact@seomatic.ai with your site address and a screenshot. A person replies, usually within one business day.


