Skill

randy_mcp_standards

Use when creating or modifying MCP servers in this repo. Enforces secret-free configs, uv/uvx entrypoints, and .env.example patterns.

Install

npx claudepluginhub randypitcherii/rpw-agent-marketplace --plugin rpw-building

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Required standards for any MCP server in the `rpw-building` plugin and this repository. Apply when adding new servers or updating existing ones.

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

MCP Integration

6 files

Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.

plugin-dev

83.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Randy MCP Standards

Required standards for any MCP server in the rpw-building plugin and this repository. Apply when adding new servers or updating existing ones.

Hard Rules

Always include a sample MCP config JSON — every server must ship a copy-pasteable config example.
Never embed secrets in MCP config JSON — no API keys, tokens, or credentials in config files.
Use uvx/uv run as entrypoint — secrets are loaded dynamically from .env at runtime by run_mcp.py or equivalent launcher.
Never commit .env — ensure .gitignore includes .env and **/.env.
Provide .env.example — document required env vars with placeholder values (no real secrets).
Use server sample file naming — <server>.mcp.json (e.g. google_tasks.mcp.json, google_docs_with_subtabs.mcp.json).
plugin-root .mcp.json — every plugin must ship a root .mcp.json at the repo/plugin root that wires all MCP servers.
Use ${CLAUDE_PLUGIN_ROOT} for paths — MCP config args must use ${CLAUDE_PLUGIN_ROOT} placeholders (not machine-specific absolute paths) for Claude portability.

Per-Server Required Files

File	Purpose
`run_mcp.py`	Loads `.env`, validates required vars, execs the MCP server with enriched env
`.env.example`	Template listing required variables (e.g. `GOOGLE_CLIENT_ID=`, `GOOGLE_CLIENT_SECRET=`)
`<server>.mcp.json`	Sample config for Claude Desktop / Cursor; command/args only, no secrets
`pyproject.toml`	Project metadata and dependencies

Sample MCP Config Pattern

{
  "_comment": "Sample config for <server>. Merge into your MCP client config. No secrets.",
  "mcpServers": {
    "<server-name>": {
      "command": "uv",
      "args": ["run", "--project", "${CLAUDE_PLUGIN_ROOT}/mcp-servers/<server>", "python", "${CLAUDE_PLUGIN_ROOT}/mcp-servers/<server>/run_mcp.py"]
    }
  }
}

Use uv run for local development; uvx for published packages.
Paths in args must use ${CLAUDE_PLUGIN_ROOT} placeholders for Claude portability.
Auth/credentials come from .env loaded by run_mcp.py.

Cursor Follow-on Config Generation

When generating MCP config for Cursor, derive from the plugin-root .mcp.json and ${CLAUDE_PLUGIN_ROOT} pattern. Cursor reads MCP config from its settings; ensure generated config uses the same portable path placeholders so it works across machines.

.gitignore Checklist

Ensure the repo .gitignore contains:

.env
**/.env