debug_error — Pine Script v6 Documentation MCP Prompt

debug_error is one of 3 prompts on the Pine Script v6 Documentation MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke debug_error from your client

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

Other prompts on this server

• convert_v5_to_v6
• explain_function

Pine Script v6 Documentation 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.