parcadei

mcp-scripts

MCP Script Rules

parcadei 3,930 299 Updated 8mo ago
GitHub

Install

npx skillscat add parcadei/continuous-claude-v3/mcp-scripts

Install via the SkillsCat registry.

About this skill

This skill defines conventions for writing scripts in the scripts/ directory, including using CLI arguments, proper tool naming with double underscores, and importing from runtime.mcp_client instead of servers/ directly. It solves the problem of inconsistent script development and parameter handling across the codebase. Developers should use it when creating or modifying scripts to ensure compatibility with the MCP tool calling system.

SKILL.md

MCP Script Rules

When working with files in scripts/:

DO

  • Use CLI arguments for all parameters (argparse)
  • Include USAGE docstring at top of file
  • Use call_mcp_tool("server__tool", params) pattern
  • Handle errors gracefully with informative messages
  • Print results to stdout for Claude to process

DON'T

  • Hardcode parameters in the script
  • Edit scripts to change parameters (use CLI args instead)
  • Import from servers/ directly (use runtime.mcp_client)

Tool Naming

Tool IDs use double underscore: serverName__toolName

Examples:

  • morph__warpgrep_codebase_search
  • ast-grep__ast_grep
  • perplexity__perplexity_ask

Testing

Test with: uv run python -m runtime.harness scripts/<script>.py --help