Claude Code
One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.
Kiro SEO: Turn Search Console Data Into a Spec
Kiro plans work as specs before it writes code. Add SEOmatic with one mcp.json block, and those specs can start from real data: which pages lose clicks on Google, which ones Google skipped, and where AI answers leave you out. Then Kiro fixes the cause in your code, or on paid plans stages the fix in your CMS for your approval.
- One mcp.json block for the Kiro IDE and CLI
- An API key that stays connected across CLI sessions
- SEO specs built from your own Search Console
Kiro
About SEOmatic for Kiro
SEOmatic is a hosted MCP server that Kiro reads from its mcp.json. The Kiro IDE and the Kiro CLI send your SEOmatic API key with each request, or sign in with OAuth, and call SEOmatic's SEO tools on one workspace.
Last Updated
November 2026
Requirements
Kiro (IDE or CLI), signed in, and a free SEOmatic account. Create an API key in Settings, AI Agents, API Keys.
Pricing
Free to connect. Search Console, audits and page checks have no limit; market data uses 5 free questions a month (plus a one-time 10 when you connect Search Console). Paid plans add agents that stage fixes for your approval. See pricing.
Full Docs
Endpoint, auth, every tool and what it costs: SEOmatic MCP server docs.
Kiro for SEO, Grounded in Your Search Console
What Kiro Can Do for Your SEO
SEO Specs From Real Data
Kiro writes requirements, a design and tasks for your SEO fixes, with the Search Console numbers behind each one.
Index Problems Traced to the Code
For pages Google skipped, Kiro finds the noindex, canonical or redirect in your repo that explains it.
Titles Rewritten From Real Queries
It reads the searches each page appears for and rewrites the title and description in your code to match.
Checks That Run on Their Own
Kiro hooks can run an SEO check on the pages you edit, so a missing title or stray noindex is caught before you commit.
AI Answer Gaps
Which questions ChatGPT, Claude and Google AI Overviews answer without naming you, and who they name instead.
CMS Fixes You Approve
For WordPress, Shopify, Webflow and other CMS sites, Kiro stages fixes in SEOmatic on paid plans for your approval.
Kiro is built to plan before it codes. Give it your search data, and its plans start from the pages that actually lose traffic.
Example: Ask Kiro About Your Site
An example on the Acme Plumbing demo site. You ask Kiro:
“Write a spec to fix the SEO on our three service pages, based on our Search Console data.”
Kiro calls SEOmatic:
seomatic gsc_performance: Jul 14 to Oct 11 (90 days), by pageseomatic gsc_indexing: /emergency-plumberwrite .kiro/specs/service-page-seo/requirements.md
Kiro answers:
I wrote the spec in .kiro/specs/service-page-seo/, from Jul 14 to Oct 11 (90 days):
- /emergency-plumber is “Crawled, currently not indexed”. Requirement: fix the canonical, which points to the home page.
- /water-heater-repair has 9,860 impressions and a 1.4% CTR at position 7.6. Requirement: a title that matches “water heater repair” and “same day”.
- /drain-cleaning-cost ranks 10.9 and never states a price. Requirement: a price range section and an FAQ.
Review the requirements and I will write the design and tasks. Nothing changes on the live site until you merge and deploy.
Also try:
- “Which pages has Google not indexed, and why?”
- “Audit the site before I deploy”
- “Add a hook that checks titles when I save a page”
- “Do AI answers cite our pages?”
SEO Specs, Not Guesses
Kiro's specs break work into requirements, a design and tasks before any code changes. With SEOmatic connected, the requirements come from your data instead of a hunch:
- Requirements: Kiro asks SEOmatic which pages lose clicks, rank on page two or are not indexed, and writes one requirement per page, with the numbers and date range.
- Design: Kiro reads your templates and decides where each fix belongs, such as a title template, a canonical helper or a schema component.
- Tasks: Kiro works through the fixes one by one, and you review each change.
A few days after you deploy, ask Kiro to check the same pages again in Search Console.
Why This Page Uses an API Key First
Kiro supports OAuth sign-in for MCP servers, and the IDE handles it well. The Kiro CLI has an open issue (issue 11850) where it renews your sign-in during a session but does not save the renewal. SEOmatic replaces the sign-in token on every renewal, for your safety, so the next CLI session holds an old token and asks you to sign in again.
An API key avoids the sign-in step, so the same block works in the IDE and the CLI, session after session. The key belongs to one SEOmatic workspace, and you can delete it in SEOmatic at any time.
Kiro SEO Prompts to Try
Ask these in Kiro's chat, with your site's repo open:
- “Write a spec to fix the SEO on our three service pages, based on our Search Console data.”
- “List the pages Google has not indexed and find the cause in this repo.”
- “Which pages get impressions on Google but few clicks? Rewrite their titles.”
- “Audit the site before I deploy and fix anything that would hurt rankings.”
- “My organic clicks fell this month. Which pages lost them, and why?”
- “Which questions do AI assistants answer without citing us?”
The SEO Tools Kiro Gets
- Search Console performance and insights: clicks, impressions, CTR and position, striking-distance queries, cannibalization and period comparisons, with exact date ranges.
- Indexing checks: whether Google indexed a URL, and why not.
- Site audit and page scores: up to 30 pages per crawl, or a 0 to 100 score for one URL.
- AI visibility and citations: where ChatGPT, Claude and Google AI Overviews mention or cite you.
- Keyword and backlink research, from your free questions or your paid plan's credits.
- Tasks and campaigns on paid plans: fixes for CMS sites, staged for your approval.
Every tool, with its parameters and cost, is in the SEO MCP server reference.
How It Works, Step by Step
- You ask Kiro a question about your site, or ask it for a spec.
- Kiro calls the SEOmatic tools it needs, sending your API key with each call.
- SEOmatic returns your real data and its own analysis, with exact date ranges.
- Kiro writes the plan, reads the matching files and edits the code. You review each change.
- For CMS sites on a paid plan, Kiro stages the fix in SEOmatic instead. You approve it, and SEOmatic applies it with a rollback point.
How to Connect SEOmatic to Kiro
About two minutes, with Kiro installed and signed in.
- Create an API key. In SEOmatic, open Settings, AI Agents and create an API key. Copy it; it starts with smk_live_.
- Open Kiro's MCP config. In the Kiro IDE, open the Command Palette and run Kiro: Open user MCP config (JSON), or use the Open MCP Config icon in the Kiro panel. If the MCP options are missing, open Settings, search for MCP and turn on MCP support. For the CLI, open ~/.kiro/settings/mcp.json in any editor.
- Paste the SEOmatic block. Add the seomatic entry under mcpServers with the URL https://app.seomatic.ai/api/mcp and your key in the Authorization header. Keep autoApprove set to ["*"], or list only the tools you want to run without a prompt; without it Kiro asks before every SEOmatic call. Keep any servers already there, and save. Kiro reconnects as soon as the file is saved.
- Check the connection. In the Kiro IDE, open the Kiro panel's MCP servers tab and check that seomatic shows as connected and lists its tools. In the CLI, run /mcp inside a session, or kiro-cli mcp status --name seomatic from your shell.
- 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.
Kiro setup
// ~/.kiro/settings/mcp.json
// (or .kiro/settings/mcp.json for one workspace)
{
"mcpServers": {
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp",
"headers": {
"Authorization": "Bearer smk_live_..."
},
"autoApprove": ["*"]
}
}
}
// OAuth instead: drop the headers
{
"mcpServers": {
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp",
"autoApprove": ["*"]
}
}
}
// CLI check
kiro-cli mcp status --name seomatic
// CLI sign-in, OAuth route only (inside a session)
/mcp auth seomaticA workspace file (.kiro/settings/mcp.json) wins over the user file when both exist, and a custom agent's own mcpServers field wins over both, so check those if Kiro seems to ignore a change. Keep API keys in the user file, not in a shared repo. Without autoApprove, Kiro asks you to approve each SEOmatic tool call; ["*"] approves them all, or name the tools you trust. In a folder you have not trusted, the Kiro CLI asks before every MCP call anyway: choose Trust, continue when it asks. If Kiro shows a client registration or redirect error while you use a key, the key was rejected and Kiro fell back to sign-in: create a new key and paste it again.
API key, OAuth or skills?
| Route | Best for | How |
|---|---|---|
| mcp.json with an API key | Most people: works in the Kiro IDE and the Kiro CLI | Paste the block above into ~/.kiro/settings/mcp.json with your key in the Authorization header. The Kiro CLI reads the same file; kiro-cli mcp add only takes a --command, so there is no one-line command for a remote server. |
| mcp.json with OAuth | The Kiro IDE, if you would rather sign in than copy a key | Use only the url and autoApprove, without headers. Kiro opens the sign-in in your browser. If Kiro lists only check_site and connect_seomatic, it is not signed in yet: in the CLI, /mcp auth seomatic starts the sign-in. The Kiro CLI may ask you to sign in again in each new session. |
| Skills only | Running SEO checks through the SEOmatic CLI | npx skills add Minh42/seomatic-mcp -a kiro-cli, with SEOMATIC_API_KEY set. |
Pick mcp.json with an API key. It works the same in the IDE and the CLI, and it stays connected when you start a new CLI session. You can switch to OAuth later by removing the headers.
Kiro or Amazon Q Developer: Which One Is This?
Kiro is AWS's agentic coding tool: an IDE that plans work as specs, plus the Kiro CLI. SEOmatic connects to both through the same mcp.json file.
- Amazon Q Developer stopped taking new signups on May 15, 2026, and Kiro is its successor. If you set up MCP servers in Q, add SEOmatic to Kiro with the block on this page.
- Other agentic IDEs, like Cursor or Google Antigravity, have their own setup on their own pages.
This page covers Kiro, in the IDE and the CLI.
What Is Free and What Is Paid
Connecting is free, and so is the SEOmatic account behind it: no card. Free covers the diagnosis with no limit: Search Console reports and insights, site audits of up to 30 pages, live page analysis, and your AI visibility results.
Live market data, like keyword volumes, backlink profiles and competitor domains, uses free questions: 5 a month, plus a one-time 10 bonus questions when you connect Google Search Console. One question covers up to 5 lookups.
Paid plans remove the question limit and add the treatment: agents stage fixes on your site (titles, descriptions, content updates, technical fixes, internal links) and run campaigns and fresh AI visibility scans. Every paid plan starts with a 14-Day Trial for $1, credited to your first payment. See pricing.
Kiro's own usage is billed by Kiro. SEOmatic questions count only the SEOmatic tool calls, not the specs or code Kiro writes.
Nothing Changes on Your Site Without Your Approval
Kiro works in your repo and in SEOmatic, and both keep you in charge. In your repo, Kiro writes specs and code that you review before anything ships. In your CMS, it can only stage a fix in SEOmatic. The API key you give Kiro can be deleted in SEOmatic at any time. A staged change is a proposal: it says what will change and why, and in Approval mode 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.
Keep Exploring
Using another agentic IDE? See Google Antigravity, Cursor and Kilo Code. Prefer the terminal? See Claude Code SEO. Learn what powers the answers: page indexing checks, technical SEO fixes and meta tags. All agents: AI SEO agents in every assistant. Full reference: SEO MCP server docs.
Using another agent? See Google Antigravity, Cursor, Claude Code, or every AI agent.
Frequently Asked Questions
How do I connect SEOmatic to Kiro?
Create an API key in SEOmatic under Settings, AI Agents. In Kiro, open the Command Palette and run Kiro: Open user MCP config (JSON), which opens ~/.kiro/settings/mcp.json. Add a server named seomatic with the URL https://app.seomatic.ai/api/mcp, the header Authorization: Bearer followed by your key, and autoApprove set to ["*"] so Kiro does not ask before each call, then save.
Why use an API key instead of signing in?
The Kiro CLI has an open issue (11850 on the kirodotdev/Kiro repo) where it renews your sign-in during a session but does not save the renewal. SEOmatic replaces the sign-in token on each renewal, so the next CLI session asks you to sign in again. An API key skips the sign-in step and stays connected in both the IDE and the CLI.
Can I use OAuth in Kiro instead?
Yes, if you prefer. Remove the headers and keep the url and autoApprove. Kiro opens the SEOmatic sign-in in your browser. If Kiro lists only check_site and connect_seomatic, it is not signed in yet: in the CLI, run /mcp auth seomatic to start the sign-in. If the CLI keeps asking you to sign in with each new session, go back to the API key.
Does one setup cover the Kiro IDE and the Kiro CLI?
Yes. Both read ~/.kiro/settings/mcp.json, so adding SEOmatic there once makes it available in each. A workspace file at .kiro/settings/mcp.json limits it to one project.
I used MCP servers in Amazon Q Developer. What now?
Amazon Q Developer stopped taking new signups on May 15, 2026, and Kiro is its successor. Add SEOmatic to Kiro with the block on this page. Your SEOmatic account and data stay the same.
Can Kiro fix SEO problems in my code?
Yes. It reads your Search Console data through SEOmatic, writes a spec if you ask, finds the cause in your repo, such as a wrong canonical or a weak title template, and edits the files. You review each change and deploy when you are ready.
Are the numbers real?
Yes. They come from your own Google Search Console through SEOmatic, with exact date ranges such as Jul 14 to Oct 11, 90 days. SEOmatic tells the agent to state only numbers that came from a tool result.
Is SEOmatic for Kiro free?
Yes. Connecting and the SEOmatic account are free, with no card. Search Console reports, site audits and page checks are free with no limit. Live market data (keyword volumes, competitors, backlinks) uses free questions: 5 a month, plus a one-time 10 when you connect Search Console. Paid plans remove the limit and add agents that stage fixes, with a 14-Day Trial for $1, credited to your first payment.
Can it change my site without asking?
No. By default every change SEOmatic proposes waits for your approval before it touches your site, and your assistant is told never to approve on its own. Approved changes are stored with the page's previous state, so any edit to an existing page can be rolled back. If you later want low-risk fixes to go ahead on their own, you can turn that on in your autonomy settings; changes to your URLs or indexing, and new content, still wait for you.
Kiro does not show the SEOmatic tools. What now?
Check that mcp.json is valid JSON, that the Authorization value starts with Bearer and a space, and that the key has not been deleted in SEOmatic. If a workspace mcp.json exists, it wins over your user file, and a custom agent's own mcpServers wins over both. In the IDE, the Kiro panel's MCP servers tab shows the status; in the CLI, run /mcp or kiro-cli mcp status --name seomatic. If seomatic lists only check_site and connect_seomatic, Kiro is not sending your key: check the headers block. If the tools are there but Kiro asks before every call, add autoApprove, and in the CLI trust the folder.
Do I need a Google Cloud project?
No. You connect Search Console to SEOmatic once with a normal Google sign-in, and Kiro reaches it through SEOmatic. There is no service account to create.
SEOmatic in other AI agents
Same server, same tools, same approval rules. Pick the agent that fits the job.
Codex
Two commands give Codex your Search Console data, so it fixes SEO where the bug lives: in your code.
Grok Build
Two commands give Grok Build your real Search Console data, so it can find what costs you clicks and fix it in the code.
Kimi K3
Kimi K3 in Kimi Code CLI, reading your real Search Console and fixing what it finds in your repo.
DeepSeek
DeepSeek, working from your real Search Console data through the SEOmatic plugin for DeepSeek Harness.
Cursor
One mcp.json entry, and Cursor's agent works from your real Search Console data while it edits your code.