@cooperco/nuxt-layers-mcp

MCP server that exposes CooperCo Nuxt layer documentation as structured resources for AI assistants.

—

Why

AI assistants in downstream projects can't see what the layers provide without digging through node_modules. This server exposes that documentation on demand via MCP resources.

Setup in consumer projects

Add to your project's .mcp.json:

{
  "mcpServers": {
    "cooperco-layers": {
      "command": "npx",
      "args": ["@cooperco/nuxt-layers-mcp"]
    }
  }
}

Once configured, AI assistants that support MCP can read the resources listed below to understand what the CooperCo layers provide.

Resources

| URI | Name | Description | |---|---|---| | cooperco://layers/overview | CooperCo Nuxt Layers — Overview | Available layers, npm package names, installation, dependency chain, and common setup patterns | | cooperco://layers/base | Base Layer | Foundational Nuxt 4 layer — ESLint, i18n, a11y, hints, optional Loggly logging, useLogger() composable | | cooperco://layers/ui | UI Layer | Nuxt UI v4, Tailwind CSS 4, icon sets (Lucide, SimpleIcons), app config defaults | | cooperco://layers/seo | SEO Layer | Sitemap generation and robots.txt for Nuxt projects — zero config needed for basic usage |

—

For maintainers: Working on this package

Repository layout

• Package root: mcp-server
• Source: mcp-server/src/
  • index.ts — server entry point
  • resources/ — one file per resource (overview.ts, base.ts, ui.ts, seo.ts)
• Built output: mcp-server/dist/

Development scripts

# From mcp-server
npm install
npm run build        # compile TypeScript

Test with the MCP inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Publishing to npm (tag-based)

This package is published via GitHub Actions when you push a tag that matches mcp-vX.Y.Z.

High-level flow:

• Bump the version in mcp-server/package.json (SemVer)
• Commit and push to main
• Create and push a tag mcp-vX.Y.Z matching the version
• CI checks whether the version exists on npm and publishes if not

Important notes:

• Do NOT rely on npm version to create the tag (it creates vX.Y.Z). Create mcp-vX.Y.Z yourself.
• publishConfig.access is set to public; publishes are public to npmjs.
• The workflow skips if the exact version already exists.

Step-by-step

1. Bump version without creating a tag:

cd mcp-server
npm version patch --no-git-tag-version  # or minor | major

2. Commit and push:

git add mcp-server/package.json
git commit -m "chore(mcp): bump version"
git push origin main

3. Tag and push:

cd mcp-server
VERSION=$(node -p "require('./package.json').version")
cd ..
git tag "mcp-v$VERSION"
git push origin "mcp-v$VERSION"

4. CI will publish

• Workflow: .github/workflows/publish-mcp.yml
• Auth: NPM_TOKEN GitHub secret

Troubleshooting

• Version exists: bump again and retag
• 401/403: ensure NPM_TOKEN is configured and has access