reg_watch — Polyform MCP Prompt

reg_watch is one of 10 prompts on the Polyform MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke reg_watch from your client

• Claude Code Polyform Prompt/reg_watch run in your project directory
• Claude Desktop Polyform Prompt/reg_watch ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Polyform Prompt/reg_watch ~/.cursor/mcp.json
• VS Code Polyform Prompt/reg_watch .vscode/mcp.json
• Zed Polyform Prompt/reg_watch ~/.config/zed/settings.json
• Windsurf Polyform Prompt/reg_watch ~/.codeium/windsurf/mcp_config.json
• Cline Polyform Prompt/reg_watch ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Polyform Prompt/reg_watch ~/.gemini/settings.json
• Grok Polyform Prompt/reg_watch .mcp.json (in your project root)
• ChatGPT Polyform Prompt/reg_watch Settings → Connectors → Advanced → Developer mode
• Claude.ai Polyform Prompt/reg_watch Settings → Connectors → Add custom connector
• LangChain Polyform Prompt/reg_watch pip install langchain-mcp-adapters

Other prompts on this server

• vet_used_car
• domain_due_diligence
• location_brief
• token_due_diligence
• sanctions_screen
• drug_safety
• insider_activity
• company_360
• vet_business

Polyform also offers 2 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.