mcpField
M
mcp-scripts

mcp-scripts

github.com/parcadeiDevelopment3.9k494 installsUpdated 39w ago
Repository

About mcp-scripts

mcp-scripts is a skill for writing scripts in a project’s `scripts/` directory. It defines CLI argument, MCP tool-call, error-handling, and output conventions for scripts intended for Claude.

Key features

  1. 01CLI arguments for parameters
  2. 02Required usage docstrings
  3. 03MCP tool calls via runtime pattern
  4. 04Graceful error reporting
  5. 05Results printed to stdout

Use cases

  1. 01Create scripts that call MCP tools
  2. 02Keep script parameters out of source code
  3. 03Check scripts with the runtime harness

MCP support

It documents the `call_mcp_tool("server__tool", params)` pattern for invoking MCP tools through `runtime.mcp_client`.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill mcp-scripts

After installing, type/mcp-scriptsin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported