Skip to main content
Glama
205,128 tools. Last updated 2026-06-15 09:58

"Pine Script" matching MCP tools:

  • List all available Pine Script v6 documentation files with descriptions, organized by category. Use to select a file for further reading.
    MIT
  • Resolves exact Pine Script API terms and known concepts to provide precise documentation for functions and vocabulary.
    MIT
  • Search Pine Script v6 documentation for relevant sections. Multi-word queries require all terms. Returns previews with hints to retrieve full content.
    MIT
  • Access a specific Pine Script v6 documentation file using its path. Use limit and offset to manage token usage for large files.
    MIT
  • Get Pine Script v6 functions filtered by namespace. Use this to see available functions before writing Pine Script code.
    MIT
  • Read the current Pine Editor source code from TradingView. The Pine Editor must be open to fetch the script content.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • MCP server providing Pine Script v6 documentation. Enables AI to: Look up Pine Script functions and validate syntax Access official documentation for indicators, strategies, and visuals Understand Pine Script concepts (execution model, repainting, etc.) Generate correct v6 code with proper function references

  • INE Spain (Instituto Nacional de Estadística) Tempus3 JSON API MCP.

  • Save and commit the current Pine Script indicator, then reload it on the chart with one action.
    MIT
  • Replace the current Pine Script code in TradingView's Pine Editor with new source code, including the required version header.
    MIT
  • Read a specific Pine Script v6 documentation file. For large files (ta.md, strategy.md, collections.md, drawing.md, general.md) prefer list_sections() + get_section() to avoid loading 1000-2800 line files into context.
    Connector
  • Fast lookup for exact Pine Script API terms and known concepts. Use for exact function names and Pine Script vocabulary (e.g., "ta.rsi", "strategy.entry", "repainting", "request.security"). For natural language questions, read the docs://manifest resource for routing guidance, then use get_doc() or list_sections() + get_section().
    Connector
  • Get valid Pine Script v6 functions, optionally filtered by namespace. Use before writing Pine Script to see which functions exist. For checking a single function name, use validate_function() instead.
    Connector
  • Lists Pine v6 feature coverage topics with status (supported, partial, unsupported, via_transpiler) and summary to verify compatibility before writing or porting strategies.
    MIT
  • Run deterministic backtests of PineScript v6 strategies on your local machine. Transpile Pine to C++, execute against OHLCV CSV data via Docker, and keep all data private.
    MIT
  • Update an inSCADA script by replacing its code with a new Nashorn ES5 compliant script. Requires script ID and code, and prior reading with get_script.
    MIT
  • Create a post-install script to automate VPS setup tasks after virtual machine installation. The script saves to /post_install and executes with output logged to /post_install.log.
    MIT