Claude Code + Semurai
Claude Code for SEO starts with real data. Add the Semurai MCP server from your terminal, and Claude Code works with your keyword data, rankings, Search Console and site audits while it edits your repository. Run Semurai prompts as slash commands, save reports next to your code and share the setup with your team. OAuth sign-in, no API keys.
Claude Code MCP · local, project or user scope
Add it from your terminal
claude mcp add --transport http --scope user semurai https://api.semur.ai/mcpSetup
One command adds the server, one sign-in links your Semurai account. After that, Semurai is there in every project.
In your terminal, run claude mcp add --transport http --scope user semurai https://api.semur.ai/mcp.
Start Claude Code in any project, run /mcp and pick semurai.
Semurai opens in your browser. Sign in, pick a default workspace and click Allow.
Ask Claude Code in plain language, or type / to run one of the Semurai prompts.
claude mcp add --transport http --scope user semurai https://api.semur.ai/mcpclaude mcp login semuraiGood to know
/mcp without claude mcp add.--scope user makes Semurai available in all your projects. The other scopes are explained below.claude mcp list, or see one server with claude mcp get semurai.Why connect
Claude Code already knows your files. Semurai tells it how those pages do in search.
Rewrites a title from the page content alone.
Rewrites it for pages Search Console shows with many impressions and few clicks.
Picks headings without knowing what people search.
Checks volume, difficulty and intent for each heading first.
Forgets the keywords once a new page ships.
Adds the new page’s keywords to rank tracking before it goes live.
Leaves its next steps in the terminal.
Puts next steps on your Semurai task board.
Use cases
Terminal-first SEO for sites built from code: content in Markdown, templates in the repository, changes reviewed as a diff.
Astro, Next.js, Hugo or a docs folder: Claude Code reads your content files, and Semurai tells it which keywords each page should go after.
Type / and run seo_article, competitor_gap_report or weekly_seo_report like any other Claude Code command, from the folder you work in.
The weekly SEO report lands in the repository as a Markdown file: rankings, traffic, site health, content results, open tasks and next steps.
Claude Code compares your domain with up to five competitors and puts the topics worth a page on your Semurai task board, each with a short how-to.
Before a new page ships, Claude Code adds its target keywords to rank tracking, up to 50 per call, and Semurai queues a first check.
Commit the project setup once. Each developer signs in to Semurai separately, and what they can do follows their role in each workspace.
Example
The team’s .mcp.json, one slash command, and a report file that sits next to your code.
/semurai:weekly_seo_report
Week 44 compared with week 43. Rankings: 7 keywords up, 3 down. The biggest moves:
| Keyword | Position | Change |
|---|---|---|
| cold brew ratio | 6 | +5 |
| moka pot grind size | 11 | +4 |
| decaf espresso beans | 14 | -3 |
| french press coffee ratio | 9 | -2 |
Search Console: 3,180 clicks (+9%), CTR 2.4%. Site health 86/100, 7 open tasks. Shall I save the report as reports/seo-week-44.md and add the five next steps to the task board?
Yes, both.
Done. reports/seo-week-44.md holds all six sections, from rankings to next steps, and the five tasks are on your Semurai board.
Prompts to try
Scopes
Claude Code keeps every MCP server in a scope. Pick the one that matches who should use Semurai, and where.
| Scope | Who uses it | Where it works | Stored in |
|---|---|---|---|
| local (default) | Only you | Only the current project | ~/.claude.json, under that project |
| project | Everyone who works in the repository | This project | .mcp.json in the project root |
| user | Only you | All your projects | ~/.claude.json |
The command at the top of this page uses --scope user. Leave the flag out for a local setup, or use --scope project to write the team file.
Commit this file to the root of your repository, or run the command with --scope project. Claude Code asks each person to approve a project server before it uses it, and then each person signs in to Semurai with their own login.
{
"mcpServers": {
"semurai": {
"type": "http",
"url": "https://api.semur.ai/mcp"
}
}
}Prompts and skills
Semurai’s six ready-made prompts become slash commands in Claude Code, and they work well next to your own skills.
Type / in Claude Code and the Semurai prompts appear in the menu as /semurai:seo_article (MCP) and so on. /mcp__semurai__weekly_seo_report runs one as well.
/semurai:seo_article: topic, focus keyword, language/semurai:competitor_gap_report: competitor domain/semurai:weekly_seo_report: no arguments/semurai:monthly_content_plan: month, focus/semurai:store_product_seo: store, category/semurai:social_week: topic, channelsIn permission rules, Semurai’s tools are named mcp__semurai__<tool>, for example mcp__semurai__research_keywords.
You do not have to choose. A skill teaches Claude how to do a task: instructions in a folder that Claude loads when the task comes up. The Semurai server gives Claude live data and actions in your workspace.
Other assistants
The same server address and the same Semurai account work in every assistant below.
FAQ
Run claude mcp add with the transport, scope, name and address. For Semurai: claude mcp add --transport http --scope user semurai https://api.semur.ai/mcp. Then run /mcp in Claude Code, pick semurai, sign in to Semurai in the browser and click Allow.
Give it search data, then let it work where your content lives. With Semurai connected over MCP, Claude Code checks keyword metrics, rankings and Search Console while it edits titles, headings and content files in your repository, runs the weekly SEO report as a slash command and puts next steps on your Semurai task board.
User scope if you want Semurai in every project on your machine. Project scope if the whole team works on one site and should share the setup through .mcp.json. Local scope, the default, keeps it to you and the current project.
Local and user servers are stored in ~/.claude.json, project servers in .mcp.json in the project root. claude mcp list shows every configured server, and claude mcp get semurai shows the Semurai entry.
Type / and pick a Semurai prompt from the menu, for example /semurai:seo_article (MCP) or /semurai:weekly_seo_report (MCP). Typing /mcp__semurai__weekly_seo_report runs the weekly report as well.
Yes. Add Semurai with project scope, or commit .mcp.json with the semurai entry. Claude Code asks each person to approve the project server, then everyone signs in to Semurai as themselves and works within the role they have in each workspace.
claude mcp logout semurai clears the stored sign-in, and claude mcp remove semurai then removes the server from your configuration. To end access on the Semurai side, disconnect Claude Code in Settings → AI assistants (MCP).
Yes, with the full server added under its own name: run claude mcp add --transport http --scope user semurai-full https://api.semur.ai/mcp/full, then claude mcp login semurai-full (or pick semurai-full in /mcp) and click Allow. Claude Code can then generate images into your media library and get back each image’s address for the page it is editing, or create Canvas and Creative Studio designs from a brief. It can also answer the designer’s questions, revise a design and save its pages to the media library as PNG, JPG or PDF. Your semurai entry keeps working as before, and graphics use the workspace’s usage limits.
Edits to your files stay in your repository until you commit and deploy. Semurai marks its tools that change something live, such as publishing to WordPress or queueing a social post, and Claude Code checks with you before it runs one.
Create your Semurai account, run one command and ask Claude Code about your site.
