Norma MCP Server

Deterministic AI code review, with an audit record. Governance inside the agent loop.

Norma gives your coding agent the rules for your detected stack before it writes, checks each file against them, and records the outcome. The same file and the same rules return the same verdict every time, so what you get back is a record you can show someone rather than an opinion that changes between runs.

• Remote server (Streamable HTTP): https://api.qualityclouds.ai/mcp

• Auth: OAuth. Sign in via browser on first connection. Permanent free tier.

• Works with Cursor, Claude Code, Lovable, Replit and any MCP-compatible client

• Stacks covered: TypeScript, JavaScript, Python, PHP, Node, React, Vite, Supabase, FastAPI, SQLAlchemy, Adobe Magento and more

What it does

Rulesets are stack-specific and activate automatically for the stack the server detects. A single repository scan activates rulesets across six functional areas: Security, Performance, Scalability, Manageability, Maintainability and Architecture. The Supabase ruleset alone covers 12 rules, including no service-role keys outside the server, no hardcoded keys or project URLs, mandatory error checks on every mutation, no client-side JWT decoding, and rate limiting on edge functions.

The server exposes six tools:

Every session produces a structured record of what was checked, fixed and prevented. Your repository's Production-Ready Score and full findings live in your workspace at norma.qualityclouds.com.

Related MCP server: Argus MCP

How it works

A coding agent connected to Norma follows this sequence:

1. link_repository: first connection in each workspace, before any other call.

2. get_rulesets: at the start of any coding task.

3. get_rules_for_ruleset: for each relevant ruleset ID; never skipped.

4. The agent writes or modifies code, with those rules in context.

5. live_check: after each file is created or modified, before moving on.

6. register_applied_actions: after the task, using the exact rule IDs from step 3.

To work through standing issues instead of writing new code, the agent calls get_open_issues and fixes the violations from the repository's last full scan.

Try it in 5 minutes (Claude Code)

1. Add the server:

claude mcp add --scope user --transport http norma https://api.qualityclouds.ai/mcp

2. Check it connected:

claude mcp list

3. On first use, your browser opens to sign in. Free to start, no credit card.

4. Open a session in any repo and ask Claude Code to review a file against your coding standards. It will link the repository, fetch the rules for your stack, and register the results back to your workspace.

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "norma": {
      "url": "https://api.qualityclouds.ai/mcp"
    }
  }
}

Cursor will prompt you to sign in via browser on first connection.

Lovable

Lovable supports custom MCP servers as chat connectors, so Norma works with no plugin. In your project, open the connectors panel and add a custom MCP server named Norma with server URL https://api.qualityclouds.ai/mcp (HTTP transport, OAuth: your browser opens to sign in on first connection). Then send one message, and Lovable keeps it as a standing rule for the project:

From now on, for every file you create or change, run it through Norma and fix the issues it returns.

One step that is not optional: paste your repository's public GitHub URL in chat so Lovable can call link_repository. Lovable's own git remote is a tokenised URL it will not send to a third party, so until you link, live checks work but audit registration fails.

Full guide, including troubleshooting: docs/LOVABLE.md.

Links

• Sign up: norma.qualityclouds.com

• Product: qualityclouds.ai/norma

• Community, docs and support: github.com/qualityclouds/community

Built by Quality Clouds, the AI Code Governance platform, governing 950+ enterprise platform instances since 2017.