MCP Script Rules
Scanned 2/12/2026
Install to Claude Code
Skills Directorynpx -y skills add parcadei/Continuous-Claude-v3 --skill mcp-scripts --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mcp Scripts?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/parcadei-mcp-scripts)More formats (shields.io, HTML) on the badges page.
---
name: mcp-scripts
description: MCP Script Rules
user-invocable: false
---
# 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`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
