Skip to main content
Glama

QualityKit

CI npm License: MIT

Site: qualitykit.dev · Repo: github.com/maxim-at-autonomiclabs/qualitykit

Read-only SEO + AEO MCP server for Next.js codebases.

QualityKit finds what matters, explains why, proposes fixes as diffs, and verifies results. The coding agent applies approved changes. This server never writes to your repo.

Install

npm install -g qualitykit
# or run without a global install:
npx -y qualitykit

From source:

git clone https://github.com/maxim-at-autonomiclabs/qualitykit.git
cd qualitykit
npm install
npm test
npm run build

Cursor MCP config

{
  "mcpServers": {
    "qualitykit": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "qualitykit"]
    }
  }
}

Related MCP server: rankforge

Primary tools

Tool

Purpose

qualitykit.audit

Route inventory + technical/metadata/content/schema/links. Defects vs opportunities. Optional rendered HTML.

qualitykit.grow

Brand-aligned growth: Site Profile + GSC queries → scored opportunities, deprioritised demand, top 10 changes, safe vs approval.

qualitykit.get_site_profile

Living Site Profile (brand, ICP, products, voice, pages) with freshness; ephemeral draft when Cloud is offline.

qualitykit.refresh_site_profile

Cloud model refresh when Pro + MODEL_* configured; else offline host-agent brief.

qualitykit.update_site_profile

Patch profile; brand/ICP/products stay pending until user approval.

qualitykit.ai_audit

AI readiness scores (crawlability, extractability, entity clarity, citation readiness, structured understanding, topical coverage)

qualitykit.plan

Content briefs, blog architecture plan, schema, internal links

qualitykit.fix

Advise-only unified diffs / file specs for selected findings (safeAutoOnly supported); blocks irrelevant GSC ids

qualitykit.verify

Re-audit; report fixed / remaining / regressed (supports proposedFiles)

monitor.status

Latest hosted Pro run when QUALITYKIT_API_KEY is set; otherwise self_hosted / not_run

visibility.report

Search Console period metrics (incl. position/CTR), profile freshness, ranked opportunities, and changeOutcomes via Cloud when API key is set; otherwise not_connected

visibility.mark_applied

Snapshot GSC metrics for grow change ids after deploy so later visibility.report shows per-change deltas (Pro + API key)

sitemap.submit

Register /sitemap.xml with Google Search Console (and Bing when a Webmaster key is saved). Free when Cloud + Search Console are connected. Does not request indexing.

sitemap.status

Read Google/Bing sitemap processing status (pending, errors, warnings) via Cloud

Responses include additive schemaVersion + coverage fields. Never treat not_run as a pass.

Specialized tools (codebase.analyze, seo.audit, blog.scaffold, etc.) remain available but are secondary.

Resources: qualitykit://rules/technical-seo, qualitykit://rules/aeo, qualitykit://rules/content

Prompt: audit-site

Example workflow

  1. qualitykit.audit (optionally includeRendered + siteUrl)

  2. qualitykit.grow — why impressions are limited, top 10, safe vs approval

  3. Optionally qualitykit.ai_audit and qualitykit.plan

  4. Present defects and grow changes (no volumes or impression counts)

  5. Pro dashboard Opportunities: Copy MCP prompt for an item (or call qualitykit.fix with that opportunityId)

  6. Implement buildContracts in the repo; then qualitykit.verify with markApplied: true so the backlog ships

  7. qualitykit.fix with finding IDs (safeAutoOnly: true for low-risk technical diffs) when not using an opportunity card

  8. Sitemap (free): after deploy, sitemap.submit once Search Console is connected in the dashboard. Google usually rediscovers later updates without resubmitting. Check sitemap.status for processing errors.

  9. Later visibility.report for period metrics and changeOutcomes (Search Console often lags 1–3 days; deltas are correlational, not a ranking guarantee)

Empty brand/ICP on the Site Profile auto-fills from the Cloud model when MODEL_* is configured — no dashboard approve step.

MCP API key (qk_… from the dashboard) is for the local MCP to call QualityKit Cloud — not for Google OAuth. Free accounts can mint a key for sitemap.submit / sitemap.status. Connect Search Console (and optionally a Bing Webmaster API key) in the dashboard; set QUALITYKIT_API_KEY + QUALITYKIT_API_BASE=https://app.qualitykit.dev in Cursor. Pro unlocks visibility.*, grow GSC enrichment, and hosted crawls.

Findings model

Each finding includes kind (defect | opportunity), severity, impact, confidence, effort, fixSafety, evidence, why it matters, suggested fix, and verification steps.

  • Missing robots.ts → opportunity (Next defaults to allow)

  • Disallow: / → critical defect

  • Missing blog → opportunity only

AI Audit Mode

Heuristic 0–100 scores with evidence. They do not predict rankings or AI citations. FAQ schema and llms.txt are optional assessments — never required.

Open source vs Pro

Free forever ($0)

Pro ($29/mo)

Local MCP audits, qualitykit.grow, AI readiness, fixes, verify

Yes

Yes

Sitemap create/update/validate in MCP

Yes

Yes

Account / API key required

Optional (for sitemap submit)

For hosted features

sitemap.submit / sitemap.status (GSC + optional Bing)

Yes when Cloud + GSC linked

Yes

Daily hosted crawls + history

—

1 production site

Email regression alerts

—

Yes

monitor.status via cloud

Self-hosted stub

Connected

Google Search Console analytics sync

Connect for sitemap only

Yes (1 site) + impressions/queries

visibility.report + grow GSC enrichment

Offline / not_connected

Connected when GSC linked

visibility.mark_applied + per-change deltas

—

Snapshot applied recs; outcomes in report / dashboard

Free: explain why impressions are limited from the codebase, rank the next 10 changes, mark safe auto-fixes, verify after the coding agent applies approved diffs, and (with a free Cloud account) submit/monitor the sitemap. No OpenAI key inside QualityKit. Sitemap registration does not guarantee indexing or rankings.

Pro: daily crawl, history, email alerts, plus Search Console analytics sync for the monitored site. Re-ranks opportunities with real queries and shows last-28d vs prior-28d impressions/clicks. Mark recommendations applied (dashboard or visibility.mark_applied) to snapshot per-change baselines; later syncs power changeOutcomes deltas.

Hosted Pro runs at app.qualitykit.dev. The cloud app (Workers, D1, Clerk, Stripe, managed GSC) is a separate private product. This repository is the free local MCP and shared @qualitykit/engine package. Point Cursor at Pro with QUALITYKIT_API_KEY and QUALITYKIT_API_BASE=https://app.qualitykit.dev.

Local code fixes stay free. Model tokens come from your coding agent — QualityKit does not fund inference.

Safety

  • Absolute projectRoot only; skips .env* and secrets

  • Advise-only fixes — no file writes, no PR automation

  • Ask before changing AI crawler allow/disallow

  • No mass article generation or “FAQ schema = rankings” claims

Requirements

  • Node.js 18+

  • Deep analysis: Next.js (App Router for blog scaffolding)

Website

Marketing site source is in website/. Preview locally with npm install and npm run dev.

Contributing

See CONTRIBUTING.md and CODE_OF_CONDUCT.md. Security reports: SECURITY.md.

License

MIT

Available Tools

23 tools
blog.scaffoldScaffold blog architectureC

Specialized: App Router + MDX blog file specs when justified. Prefer qualitykit.plan first.

Inputs: projectRoot (required), siteUrl, contentSystem, includeCategories.

codebase.analyzeAnalyze codebaseB

Secondary: detect framework, router, routes, metadata, robots, sitemap, blog, business hints. Prefer qualitykit.audit for full audits.

Inputs: projectRoot (required), siteUrl.

content.briefCreate content briefsC

Specialized: at most three content briefs. Prefer qualitykit.plan.

Inputs: projectRoot (required), siteUrl, maxBriefs.

links.planPlan internal linksD

Specialized: contextual internal-link suggestions.

Inputs: projectRoot (required), siteUrl, proposedPaths, maxSuggestions.

monitor.statusHosted monitor statusA

Fetch latest QualityKit Cloud monitoring run when QUALITYKIT_API_KEY is set. Otherwise returns self_hosted / not_run coverage (free local mode).

Inputs: apiKey, apiBaseUrl.

opportunities.listList opportunity backlogC

Pro: list persisted grow/GSC opportunities (found|approved|shipped|snoozed). Requires QUALITYKIT_API_KEY + QUALITYKIT_API_BASE.

Inputs: apiKey, source, status, apiBaseUrl.

opportunities.syncSync opportunity backlogB

Pro: upsert grow topChanges and/or live GSC ranked opportunities into the Cloud backlog. Pass projectRoot to run local grow, or items. Returns counts by status (found N). Requires QUALITYKIT_API_KEY + QUALITYKIT_API_BASE.

Inputs: items, apiKey, siteUrl, mergeGsc, +2 more.

opportunities.updateUpdate opportunity statusB

Pro: set opportunity status to found|approved|shipped|snoozed (snooze defaults to 7 days). Requires QUALITYKIT_API_KEY + QUALITYKIT_API_BASE.

Inputs: status (required), opportunityId (required), apiKey, apiBaseUrl, +1 more.

qualitykit.ai_auditQualityKit AI auditB

AI discoverability audit: crawlability, extractability, entity clarity, citation readiness, structured understanding, topical coverage. Heuristic scores with evidence — no citation guarantees.

Inputs: projectRoot (required), siteUrl, includeRendered.

qualitykit.auditQualityKit auditA

Primary audit: route inventory, technical SEO, metadata, content, schema, links. Separates defects from opportunities. Optional rendered HTML via includeRendered+siteUrl.

Inputs: projectRoot (required), siteUrl, includeRendered.

qualitykit.fixQualityKit fix (advise-only)B

Technical findings → unified diffs/FileSpecs. page-* / gsc-query-* opportunityIds → buildContracts for the host agent (no invented page files). Never writes the repo. Use safeAutoOnly for low-risk technical fixes only.

Inputs: projectRoot (required), apiKey, siteUrl, apiBaseUrl, +4 more.

qualitykit.get_site_profileGet Site ProfileB

Return the approved Site Profile (brand, ICP, products, voice, pages, keyword relevance), confidence, and freshness. Ephemeral repo draft when Cloud is not connected.

Inputs: projectRoot (required), apiKey, siteUrl, apiBaseUrl.

qualitykit.growQualityKit grow impressionsB

Brand-aligned growth: score Search Console queries against the Site Profile, return top opportunities and deprioritised demand, with safe vs approval fixes. Uses Cloud GSC + profile when API key is set.

Inputs: projectRoot (required), apiKey, siteUrl, apiBaseUrl, +1 more.

qualitykit.planQualityKit planC

Content and architecture opportunities: briefs, blog scaffold plan, schema, internal links. Advise-only.

Inputs: projectRoot (required), siteUrl, includeBlog.

qualitykit.refresh_site_profileRefresh Site ProfileC

Prefer Cloud model refresh when Pro + MODEL_* are configured (stale fields only; material stays pending). Offline: returns a host-agent brief from repo evidence.

Inputs: projectRoot (required), apiKey, siteUrl, apiBaseUrl.

qualitykit.update_site_profileUpdate Site ProfileA

Apply a partial Site Profile patch. Brand identity, ICP, and products stay pendingApproval until approveMaterial or approvePending. Persists to Cloud when API key is set.

Inputs: patch (required), projectRoot (required), apiKey, siteUrl, +3 more.

qualitykit.verifyQualityKit verifyB

Re-audit after changes or against proposedFiles. Checks finding IDs and optional opportunityIds (route presence). Returns readyToShip; with Pro credentials, records mark_applied / shipped.

Inputs: projectRoot (required), paths, apiKey, siteUrl, +5 more.

schema.planPlan structured dataC

Specialized: Organization/WebSite/BlogPosting JSON-LD plans. No sitewide FAQ schema.

Inputs: projectRoot (required), siteUrl, includeBlogPosting.

seo.auditSEO technical auditC

Secondary alias of the audit engine. Prefer qualitykit.audit.

Inputs: projectRoot (required), siteUrl, includeRendered.

seo.plan_changesPlan SEO changesC

Secondary: technical SEO file specs. Prefer qualitykit.fix / qualitykit.plan.

Inputs: projectRoot (required), siteUrl, includeBlogHints.

seo.validateValidate SEO changesC

Specialized validation of project or proposed files. Prefer qualitykit.verify for finding-level verification.

Inputs: projectRoot (required), siteUrl, proposedFiles.

visibility.mark_appliedMark GSC recommendations appliedA

After grow → fix → verify (and deploy), snapshot Search Console metrics for grow topChanges ids so later visibility.report shows per-change impression deltas. Requires QUALITYKIT_API_KEY + QUALITYKIT_API_BASE. GSC data often lags 1–3 days.

Inputs: items, label, apiKey, changeIds, +2 more.

visibility.reportVisibility report (stub)A

Search Console growth via QualityKit Cloud when QUALITYKIT_API_KEY + QUALITYKIT_API_BASE are set. Pass period 7d|28d|90d|365d for % deltas, trend, series summary, ranked opportunities, and changeOutcomes. Otherwise not_connected stub.

Inputs: note, apiKey, period, apiBaseUrl.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.4/5.0

    Scored across 23 tools

    Disambiguation2/5

    Several tools are explicitly redundant: seo.audit is self-described as an 'alias of the audit engine' with 'Prefer qualitykit.audit', and seo.plan_changes, codebase.analyze, blog.scaffold, links.plan, content.brief, and schema.plan all overlap with qualitykit.plan/fix. The 'prefer X' notes help an attentive agent, but six planning-adjacent tools and three audit-adjacent tools create real misselection risk.

    Naming Consistency3/5

    A namespace.action pattern (qualitykit.*, seo.*, opportunities.*, visibility.*) is mostly followed, which keeps names readable and grouped. However verb forms vary widely within that pattern — bare verbs/nouns (plan, grow, fix, verify, status) mixed with verb_noun (get_site_profile, mark_applied, plan_changes) — so the surface is not fully predictable.

    Tool Count2/5

    23 tools is heavy for this domain, and the count is inflated by deprecated/secondary aliases (seo.audit, seo.plan_changes, codebase.analyze) plus three narrow specialized planners that the primary plan tool already covers. Trimming the aliases would leave a tighter, more defensible set.

    Completeness3/5

    The audit → plan → fix → verify → monitor → visibility loop is present, along with Site Profile get/refresh/update and an opportunities backlog. But update_site_profile references approveMaterial and approvePending tools that are not in this surface, leaving a dead end, and there is no project/workspace management or explicit deploy step.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to crawl live websites, audit AEO readiness, generate Schema.org @graph JSON-LD, llms.txt, ai.txt, and robots.txt, inject structured data into HTML, validate optimizations, and retrieve framework-specific code snippets.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to audit a site's technical SEO and AI-search readiness — including localhost dev servers — and retrieve rule explanations, fix templates, and generated llms.txt files so the assistant can edit the repo to resolve what it finds.
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to audit a web page in one call — title, meta description, canonical, robots, Open Graph, headings, JSON-LD, security headers and page delivery — returning each finding with its evidence and a ready patch to apply. It also compares a deploy preview against production to surface only regressions, keeps audited pages in tabs with history and daily watches, and runs Lighthouse lab tests via PageSpeed Insights.
      1
      MIT No Attribution