consolidate Cadence MCP & Claude Code skills under onflow upstream

Two related tooling stories were tangled in the original PR — they're now
consolidated to the canonical Flow Foundation paths.

SKILLS — single Claude Code marketplace
------
Hao's redesign shipped an inline 'skills/cadence/SKILL.md' (single file,
873 lines) plus 'update-ai-files.yml' CI to keep it in sync. Meanwhile,
onflow ships an official Claude Code plugin marketplace at
[onflow/flow-ai-tools](https://github.com/onflow/flow-ai-tools) — bundles
'flow-dev' plugin with the full Cadence + Flow skill suite (cadence-lang,
cadence-tokens, cadence-audit, cadence-scaffold, cadence-testing,
flow-react-sdk, flow-project-setup, flow-cli, flow-dev-setup, flow-defi,
flow-tokenomics — each with its own reference files). Inline skill is
strictly subsumed.

- skills/cadence/SKILL.md: DELETED
- .github/workflows/update-ai-files.yml: DELETED (auto-sync CI obsolete)
- content/docs/ai-tools/skills.mdx: rewritten around '/plugin marketplace
  add onflow/flow-ai-tools' install path. Skill table phrasing uses 'full
  Cadence + Flow skill suite' instead of hardcoded count (durable across
  upstream additions).

MCP — single canonical install path (flow mcp)
------
Hao's redesign also shipped 'mcp-server/' as a TypeScript / Bun standalone
package published to npm as '@outblock/cadence-mcp'. Meanwhile, Peter
Argue (Flow DX) shipped a Go-native Cadence MCP server in
[flow-cli #2306](onflow/flow-cli#2306), merged
2026-04-03 (one day after Hao's last npm publish) — inspired by Hao's
PR #285 design but implemented from scratch in Go with no extra runtime
dependencies. flow-ai-tools' install script ([scripts/install.sh
L65–98](https://github.com/onflow/flow-ai-tools/blob/main/scripts/install.sh#L65))
already registers MCP via 'flow mcp', not Hao's npm package — i.e. anyone
running the marketplace one-liner is already on the canonical path.

Two MCPs both registering as 'cadence-mcp' in Claude Code is a footgun:
same tool name, different binaries, surprising about which one served a
response. Consolidating to one canonical install path.

- mcp-server/: DELETED entirely (~7,000 lines, 21 files, ~330 tests)
- .github/workflows/publish-mcp.yml: DELETED (npm publish CI obsolete)
- content/docs/ai-tools/mcp-server.mdx: rewritten around 'flow mcp'
  (Flow CLI ≥ v2.16.0). Tool list updated to the 8 tools 'flow mcp'
  exposes (LSP-backed: cadence_check, cadence_hover, cadence_definition,
  cadence_symbols, cadence_completion + on-chain: get_contract_source,
  get_contract_code, cadence_execute_script).
- content/docs/ai-tools/integrations/{antigravity,claude,cursor,opencode}.mdx:
  install snippets all reference 'claude mcp add --scope user
  cadence-mcp -- flow mcp' (or editor-equivalent). Cursor deeplink updated.
- content/docs/ai-tools/integrations/index.mdx (NEW): per-editor matrix
  table summarizing project-context source / skills support / MCP support.
  Fixes broken '../integrations' link from skills.mdx (was 404 because
  fumadocs needs an index.mdx for directory routes).
- content/docs/ai-tools/{,integrations/}meta.json: add '...' rest token
  so any future pages added to those dirs get auto-included.
- content/docs/ai-tools/index.mdx: tweak MCP description to match new
  tool surface.
- src/routes/index.tsx (homepage hero MCP card): replaces 'npx install-mcp
  @outblock/cadence-mcp --client $CLIENT' with the 'flow mcp' install
  command. Drops the now-superfluous client + mode selectors.

(NOTE: src/routes/index.tsx homepage hero edit goes in the next commit
with the rest of the index.tsx changes — bundled with a11y to keep one
diff per file.)

DOCS / META
------
- CLAUDE.md: removed 'skills/cadence/SKILL.md' line; removed 'mcp-server/'
  line. The MCP server now lives at onflow/flow-cli/internal/mcp.
- README.md: 'AI Integration' section rewritten — Skills via flow-ai-tools
  marketplace, MCP via 'flow mcp'.

Follow-up issues for the 3 unique tools Hao's mcp-server had that 'flow
mcp' doesn't yet (cadence_security_scan, cadence_validate_args, doc-search
trio): tracked at #307 for upstream contribution to onflow/flow-cli.

Author: Aliserag

.github/workflows/publish-mcp.yml

@@ -13,15 +13,10 @@ npm run dev          # Dev server on port 3000
 npm run build        # Production build + sitemap generation
 npm run start        # Run built server (node .output/server/index.mjs)
 npm run types:check  # TypeScript + MDX type checking (fumadocs-mdx && tsc --noEmit)
-
-# MCP server (separate workspace in mcp-server/)
-cd mcp-server
-bun run build        # Build
-bun test             # All tests
-bun test:unit        # Unit tests only
-bun test:integration # Integration tests (requires Flow CLI)
 ```
 
+The Cadence MCP server is bundled with the Flow CLI as `flow mcp` (Flow CLI ≥ v2.16.0); it lives at [onflow/flow-cli/internal/mcp](https://github.com/onflow/flow-cli/tree/master/internal/mcp), not in this repo.
+
 ## Architecture
 
 ### Framework Stack
@@ -37,8 +32,6 @@ bun test:integration # Integration tests (requires Flow CLI)
 - `src/components/` — React components; `ui/` has shadcn-style primitives
 - `src/lib/` — Utilities, Fumadocs source config, Cadence TextMate grammar
 - `content/docs/` — All MDX documentation files
-- `mcp-server/` — Standalone MCP server package (published to npm as `@outblock/cadence-mcp`)
-- `skills/cadence/SKILL.md` — Compact AI skill reference, auto-updated by CI
 - `.source/` — Auto-generated by Fumadocs (do not edit)
 
 ### Routing Patterns

.github/workflows/update-ai-files.yml

@@ -8,22 +8,22 @@ Live at [cadence-lang.org](https://cadence-lang.org).
 
 ### Skills
 
-Install the Cadence skill for your AI coding agent:
+Install Flow's Claude Code skill suite from the [`onflow/flow-ai-tools`](https://github.com/onflow/flow-ai-tools) marketplace. In Claude Code:
 
-```sh
-npx skills add outblock/cadence-lang.org
+```bash
+/plugin marketplace add onflow/flow-ai-tools
+/plugin install flow-dev@flow-ai-tools
+/reload-plugins
 ```
 
 ### MCP Server
 
-Install the [Cadence MCP server](https://www.npmjs.com/package/@outblock/cadence-mcp) for AI-powered Cadence development — code checking, type info, and doc search:
+The Cadence MCP server is built into the [Flow CLI](https://developers.flow.com/tools/flow-cli) (≥ v2.16.0) as `flow mcp`. Source: [onflow/flow-cli/internal/mcp](https://github.com/onflow/flow-cli/tree/master/internal/mcp).
 
 ```sh
-npx install-mcp @outblock/cadence-mcp --client claude
+claude mcp add --scope user cadence-mcp -- flow mcp
 ```
 
-Supported clients: `claude`, `cursor`, `windsurf`, `copilot`, `vscode`
-
 ### LLM Context
 
 | Endpoint | Description |

CLAUDE.md

@@ -5,7 +5,7 @@ title: AI Tools
 Cadence is designed for AI-native development. Three integrations make Cadence documentation and language intelligence available to any AI agent:
 
 - **[Skills](/docs/ai-tools/skills)** — inject Cadence knowledge into AI coding agents with one command
-- **[MCP Server](/docs/ai-tools/mcp-server)** — give AI agents live access to documentation search and the Cadence language server
+- **[MCP Server](/docs/ai-tools/mcp-server)** — `flow mcp` from the Flow CLI: gives AI agents type checking, symbol lookup, contract source fetching, and read-only on-chain script execution
 - **[LLM Endpoints](/docs/ai-tools/llm-endpoints)** — plain-text documentation endpoints optimized for LLM context windows
 
 ## Agent integrations

README.md

@@ -4,27 +4,35 @@ title: Antigravity
 
 Configure [Antigravity](https://antigravity.dev) to work with Cadence.
 
-## Install the Cadence skill
+## Add Cadence as project context
 
-```bash
-npx skills add outblock/cadence-lang.org
+Antigravity reads project-level context files automatically. Add a `CADENCE.md` (or merge into your existing `AGENTS.md`) pointing at the [`/llms-full.txt`](../llm-endpoints) endpoint so the model has the full reference loaded on startup:
+
+```markdown
+## Cadence Development
+
+This project uses Cadence, the smart contract language for the Flow blockchain.
+Full reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
+
+Resources use `@` prefix and must be moved with `<-`. Use `access(all)` for public access (not `pub`). Capability-based access control with entitlements.
 ```
 
-Antigravity reads project-level context files automatically, so `SKILL.md` is picked up on startup.
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
 
 ## Add MCP server
 
-Add the Cadence MCP server to your Antigravity configuration:
+Add the Cadence MCP server to your Antigravity configuration — calls the Flow CLI's built-in `flow mcp` subcommand:
 
 ```json
 {
   "mcpServers": {
-    "cadence": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://cadence-mcp.up.railway.app/mcp"]
+    "cadence-mcp": {
+      "command": "flow",
+      "args": ["mcp"]
     }
   }
 }
 ```
 
-This gives Antigravity access to all [MCP tools](../mcp-server) — documentation search, code checking, type inspection, and more.
+This gives Antigravity access to all [MCP tools](../mcp-server) — Cadence code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution. Requires [Flow CLI](https://developers.flow.com/tools/flow-cli) ≥ v2.16.0.

content/docs/ai-tools/index.mdx

@@ -6,25 +6,24 @@ Configure Claude to work with Cadence via skills, MCP, or context injection.
 
 ## Claude Code
 
-### Install the Cadence skill
+### Install Flow's skill library
 
-```bash
-npx skills add outblock/cadence-lang.org
-```
-
-### Add MCP server
+The official [onflow/flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace ships the full Cadence + Flow skill suite under one plugin:
 
 ```bash
-claude mcp add cadence-mcp -- npx -y mcp-remote https://cadence-mcp.up.railway.app/mcp
+/plugin marketplace add onflow/flow-ai-tools
+/plugin install flow-dev@flow-ai-tools
 ```
 
-Or use `install-mcp` for auto-configuration:
+See [Skills](../skills) for the full skill list.
+
+### Add MCP server
 
 ```bash
-npx install-mcp @outblock/cadence-mcp --client claude-desktop
+claude mcp add --scope user cadence-mcp -- flow mcp
 ```
 
-This gives Claude Code access to all [MCP tools](../mcp-server) — documentation search, code checking, type inspection, and more.
+This registers the [Cadence MCP server](../mcp-server) — built into the Flow CLI as the `flow mcp` subcommand. Gives Claude Code access to Cadence code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution. Requires [Flow CLI](https://developers.flow.com/tools/flow-cli) ≥ v2.16.0.
 
 ## Claude Desktop
 
@@ -33,9 +32,9 @@ Add the Cadence MCP server to your `claude_desktop_config.json`:
 ```json
 {
   "mcpServers": {
-    "cadence": {
-      "command": "npx",
-      "args": ["-y", "mcp-remote", "https://cadence-mcp.up.railway.app/mcp"]
+    "cadence-mcp": {
+      "command": "flow",
+      "args": ["mcp"]
     }
   }
 }

content/docs/ai-tools/integrations/antigravity.mdx

@@ -4,31 +4,26 @@ title: OpenAI Codex
 
 Configure OpenAI Codex (the CLI agent) to work with Cadence.
 
-## Install the Cadence skill
+## Add Cadence to AGENTS.md
 
-```bash
-npx skills add outblock/cadence-lang.org
-```
-
-Codex reads project-level context files, so `SKILL.md` is picked up automatically.
-
-## Add instructions
-
-Create or update your `AGENTS.md` file in the project root:
+Codex reads `AGENTS.md` from the project root automatically. Add a Cadence section that points it at the [`/llms-full.txt`](../llm-endpoints) endpoint:
 
 ```markdown
 ## Cadence Development
 
 This project uses Cadence, the smart contract language for the Flow blockchain.
-Refer to SKILL.md for the complete language reference.
+Full reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
 
 Key conventions:
-- Use `access(all)` for public access, not `pub`
-- Resources use `@` prefix and must be moved with `<-`
+- Use `access(all)` for public access, not the deprecated `pub`
+- Resources use `@` prefix and must be moved with `<-` (never copied)
 - Always handle resources — they cannot be lost or copied
 - Use capability-based access control with entitlements
 ```
 
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
+
 ## Context injection
 
 For direct API usage, inject the Cadence documentation into the system prompt:

content/docs/ai-tools/integrations/claude.mdx

@@ -4,32 +4,34 @@ title: Cursor
 
 Configure Cursor to understand Cadence smart contracts.
 
-## Install the Cadence skill
+## Add Cadence as project context
 
-```bash
-npx skills add outblock/cadence-lang.org
-```
-
-This adds a `SKILL.md` file to your project. Cursor reads it automatically as project context.
+Cursor reads `.cursor/rules/*.mdc` files automatically. Create `.cursor/rules/cadence.mdc` and point it at the [`/llms-full.txt`](../llm-endpoints) endpoint so the model has the full reference:
 
-## Add project rules
+```mdc
+---
+description: Cadence smart contract development on Flow
+globs: *.cdc
+---
 
-You can also create a `.cursor/rules` file to reinforce Cadence-specific behavior:
+When working with `.cdc` files, follow Cadence language conventions:
+- Use `access(all)` for public access (not the deprecated `pub`)
+- Resources use `@` prefix and must be moved with `<-` (never copied)
+- Always handle resources — they cannot be lost or copied
+- Use capability-based access control with entitlements
 
-```
-When working with .cdc files, follow the Cadence language conventions.
-Refer to SKILL.md for the complete Cadence reference.
-Use resource-oriented patterns. Never copy resources — always move them with <-.
+Full Cadence reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
 ```
 
-## Add MCP server
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
 
-[![Install in Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](cursor://anysphere.cursor-deeplink/mcp/install?name=cadence&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIm1jcC1yZW1vdGUiLCJodHRwczovL2NhZGVuY2UtbWNwLnVwLnJhaWx3YXkuYXBwL21jcCJdfQ==)
+## Add MCP server
 
-Or manually add in Cursor settings:
+In Cursor settings → MCP → Add new server:
 
-- **Name**: `cadence`
+- **Name**: `cadence-mcp`
 - **Type**: `command`
-- **Command**: `npx -y mcp-remote https://cadence-mcp.up.railway.app/mcp`
+- **Command**: `flow mcp`
 
-This gives Cursor access to the Cadence [MCP tools](../mcp-server) for documentation search and code checking.
+This registers the [Cadence MCP server](../mcp-server) — built into the Flow CLI as the `flow mcp` subcommand. Gives Cursor access to Cadence code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution. Requires [Flow CLI](https://developers.flow.com/tools/flow-cli) ≥ v2.16.0.

content/docs/ai-tools/integrations/codex.mdx

@@ -6,31 +6,26 @@ Configure Google Gemini to work with Cadence.
 
 ## Gemini CLI
 
-### Install the Cadence skill
+### Add Cadence to GEMINI.md
 
-```bash
-npx skills add outblock/cadence-lang.org
-```
-
-Gemini CLI reads project context files, so `SKILL.md` is picked up automatically.
-
-### Add instructions
-
-Create a `GEMINI.md` file in your project root:
+Gemini CLI reads `GEMINI.md` from the project root automatically. Create or update it with a Cadence section that points at the [`/llms-full.txt`](../llm-endpoints) endpoint:
 
 ```markdown
 ## Cadence Development
 
 This project uses Cadence, the smart contract language for the Flow blockchain.
-Refer to SKILL.md for the complete language reference.
+Full reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
 
 Key conventions:
-- Use `access(all)` for public access, not `pub`
-- Resources use `@` prefix and must be moved with `<-`
+- Use `access(all)` for public access, not the deprecated `pub`
+- Resources use `@` prefix and must be moved with `<-` (never copied)
 - Always handle resources — they cannot be lost or copied
 - Use capability-based access control with entitlements
 ```
 
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
+
 ## Gemini API
 
 When using the Gemini API, inject Cadence context into the system instruction: