All servers · Scraping & browsing · Documents & retrieval

Pine Script v6 Documentation

io.github.paulieb89/pinescript-mcp · v0.6.17

Measured by MCP Station

Description written by the publisher, not verified

Pine Script v6 documentation lookup, function validation, and linting for AI code generation

Connect

claude mcp add --transport http pinescript-mcp https://pinescript-mcp.fly.dev/mcp

{
  "mcpServers": {
    "pinescript-mcp": {
      "url": "https://pinescript-mcp.fly.dev/mcp"
    }
  }
}

claude mcp add --transport http pinescript-mcp https://pinescript-mcp.fly.dev/sse

{
  "mcpServers": {
    "pinescript-mcp": {
      "url": "https://pinescript-mcp.fly.dev/sse"
    }
  }
}

Tools as reported by the server

• list_docs
  USE WHEN discovering what Pine Script v6 documentation is available. Returns a categorised list of doc file paths with one-line descriptions. AFTER calling this tool, call get_doc(path) for small files or list_sections(path) then get_section(path, header) for large files (ta.md, strategy.md, collect
• list_sections
  USE WHEN navigating a large documentation file before reading a specific section. Returns a newline-separated list of # and ## headers (### excluded) in the file. AFTER calling this tool, call get_section(path, header) with a header from this list. Data sourced from bundled Pine Script v6 documentat
• get_doc
  USE WHEN reading the full content of a Pine Script v6 documentation file. Returns the file content; when limit is set, a header shows the char range and offset to continue reading. AFTER calling this tool, use offset=<end> to continue if the header indicates more content is available. For large file
• get_section
  USE WHEN reading a specific named section from a Pine Script v6 documentation file. Returns the section content from the matched header to the next same-level header, with file path and line range. AFTER calling this tool, call list_sections(path) if the header was not found, or get_section() again
• search_docs
  USE WHEN finding documentation sections that match specific terms across all Pine Script v6 docs. Returns up to max_results sections ranked by match count, each with a preview and a get_section() call hint. AFTER calling this tool, call get_section(file, header) for each result you want to read in f
• get_functions
  USE WHEN browsing valid Pine Script v6 functions, optionally filtered to a namespace. Returns function names grouped by namespace (e.g. ta.*, strategy.*) or filtered to the requested namespace. AFTER calling this tool, call validate_function(fn_name) to check a specific name, or get_section() to rea
• validate_function
  USE WHEN confirming a Pine Script v6 function name is valid before using it in code. Returns a valid/invalid verdict with namespace suggestions or known replacement hints (e.g. ta.adx → ta.dmi, security → request.security). AFTER calling this tool, call get_functions(namespace) to list all valid fun
• resolve_topic
  USE WHEN looking up an exact Pine Script API term or known concept keyword. Returns the best-matching doc paths with matched keywords and a retrieval suggestion (get_doc or list_sections + get_section). AFTER calling this tool, follow the suggestion: call get_doc() for small files or list_sections()
• list_prompts
  List all available prompts. Returns JSON with prompt metadata including name, description, and optional arguments.
• get_prompt
  Get a prompt by name with optional arguments. Returns the rendered prompt as JSON with a messages array. Arguments should be provided as a dict mapping argument names to values.

Repository · Website · JSON · Text for agents · Registry updated 2026-04-04