rn-conventions-mcp

An MCP server exposing personal React Native / Expo project conventions — commit style, CI/CD templates, tooling configs — for reuse across projects via any MCP client.

Install

claude mcp add rn-conventions -- npx -y rn-conventions-mcp

Add -s user to register it once for every project on your machine instead of just the current one.

{
  "mcpServers": {
    "rn-conventions": {
      "command": "npx",
      "args": ["-y", "rn-conventions-mcp"]
    }
  }
}

Drop this into your client's MCP config (e.g. claude_desktop_config.json).

What's inside

Every file under resources/ is exposed as an MCP resource at rn-conventions://<category>/<filename>. A list_conventions tool lists them, optionally filtered by category, and get_convention returns one resource's full text by id. An inspect_project tool detects the calling project's actual framework, Expo Router, New Architecture, React Compiler, package manager, TypeScript and Jest setup, so conventions apply based on what's really there instead of assumed.

docs/

Commit & branch conventions, AI-attribution policy, CI-verification policy, the .web.tsx platform-split rule, comment style, CLAUDE.md style, tooling-stack rationale, architecture baseline.

tooling/

oxlint, oxfmt, ESLint (Expo and bare RN CLI variants), and knip configs for classic Expo, Expo Router, and bare RN CLI.

ci/

GitHub Actions workflows: type-check/lint/format/test/web-build/deadcode for Expo and RN CLI, plus a GitHub Pages web-deploy workflow.

Prompts

bootstrap-new-project (arg: projectType — expo-router | classic-expo | bare-rn-cli) — checklist for scaffolding a brand-new project against these conventions.
retrofit-existing-project — checklist for auditing an existing project and proposing an additive plan, never a blind overwrite.

Both start by checking architecture-baseline.md: New Architecture is assumed on, React Compiler is checked for rather than assumed.