# Loomaly

Connects SEO auditing to your coding assistant to spot search issues and prepare pull requests right in your repository.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: loomaly
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/loomaly/loomaly
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/mcp/loomaly

## What it does

Loomaly integrates search diagnostics into your development environment via an endpoint hosting 12 tools, including `problem` and `report`. It never edits your live domain directly. Instead, the assistant identifies top-priority SEO bugs, edits code inside your project repository, and tracks the live URL once changes deploy.

Three bundled skills (`seo`, `seo-ops`, and `weekly-loop`) cater to developers, operations, and product roles. They build weekly progress summaries with sparklines or verify conversion impact on high-value pages. First use opens a browser window for account login. On paid tiers, running out of your monthly data budget halts paid audits without overage fees.

## Requirements
- Remote server: `https://loomaly.com/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http loomaly https://loomaly.com/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add loomaly --url https://loomaly.com/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "loomaly": {
            "url": "https://loomaly.com/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "loomaly": {
            "type": "http",
            "url": "https://loomaly.com/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http loomaly https://loomaly.com/mcp
```

## When to use it
- inspect search visibility bottlenecks with framework-specific fixes
- generate pull requests addressing top priority SEO issues
- compile weekly search reports with sparkline charts
- validate live pages automatically after production deployments

## Example prompts
- Inspect mysite.com with Loomaly, resolve the top issue in this repo, and submit a pull request.
- Show our weekly visibility report and forward unresolved bugs to the dev team.
- Review the target page using `weekly-loop` to suggest the next optimization step.

## Similar
- [NessFlow](https://affpapa.org/en/nevibecode/mcp/nessflow.md) — MCP server · ★ 2
- [seo-audit](https://affpapa.org/en/nevibecode/skills/every-app-seo-audit.md) — skill · 5200 installs
- [blog-google](https://affpapa.org/en/nevibecode/skills/blog-google.md) — skill · 2500 installs
- [recover-content](https://affpapa.org/en/nevibecode/skills/recover-content.md) — skill · 2100 installs
- [anycap-ai-tool-seo](https://affpapa.org/en/nevibecode/skills/anycap-ai-tool-seo.md) — skill · 676 installs
- [Search Console MCP](https://affpapa.org/en/nevibecode/mcp/search-console-mcp.md) — MCP server · ★ 312

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md