Pine Script v6 documentation lookup, function validation, and linting for AI code generation
This MCP server provides Pine Script v6 documentation lookup, function validation, and linting to support AI code generation. It is exposed as a server with 10 tools and is associated with Pine Script and TradingView workflows, targeting skills and tooling integrations for automated Pine code authoring.
🛠️ Key Features
Pine Script v6 documentation lookup
Function validation
Linting for generated code
10 available tools
🚀 Use Cases
Validate Pine Script functions during AI-assisted code generation
Lint Pine Script v6 to catch issues before use
Reference Pine Script v6 documentation while generating trading logic
⚡ Developer Benefits
Reduce runtime errors by validating functions
Apply linting as part of an AI generation pipeline
Use MCP tooling aligned with Pine Script v6 and TradingView
⚠️ Limitations
Coverage is specific to Pine Script v6 (per server description)
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, collections.md, drawing.md, general.md).
Data sourced from bundled Pine Script v6 documentation.
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 documentation.
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 files (ta.md, strategy.md, collections.md, drawing.md, general.md), prefer list_sections() + get_section() instead.
Data sourced from bundled Pine Script v6 documentation.
Parameters3
path
string
required
Relative path to the documentation file (e.g., 'reference/functions/ta.md').
limit
integer
optional
Maximum characters to return. Use 30000 for large files. 0 = no limit.
offset
integer
optional
Character offset to start reading from.
Raw schema
{
"type": "object",
"properties": {
"path": {
"description": "Relative path to the documentation file (e.g., 'reference/functions/ta.md').",
"type": "string"
},
"limit": {
"default": 0,
"description": "Maximum characters to return. Use 30000 for large files. 0 = no limit.",
"minimum": 0,
"type": "integer"
},
"offset": {
"default": 0,
"description": "Character offset to start reading from.",
"minimum": 0,
"type": "integer"
}
},
"required": [
"path"
],
"additionalProperties": false
}
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 with a child header for a narrower subsection.
Data sourced from bundled Pine Script v6 documentation.
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 full.
Data sourced from bundled Pine Script v6 documentation.
Parameters2
query
string
required
Search terms (case-insensitive). Multi-word queries match sections containing ALL terms.
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 read its documentation.
Data sourced from bundled pine_v6_functions.json.
Parameters1
namespace
string
optional
Filter by namespace (e.g., 'ta', 'strategy', 'request'). Empty string returns all functions grouped by namespace.
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 functions in the relevant namespace if the function is invalid.
Data sourced from bundled pine_v6_functions.json.
Parameters1
fn_name
string
required
Function name to validate (e.g., 'ta.sma', 'strategy.entry', 'plot').
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() + get_section() for large files. For natural language questions use search_docs() instead.
Data sourced from bundled TOPIC_MAP and doc file content scan.
Parameters1
query
string
required
Exact Pine Script term or known concept keyword (e.g., 'ta.rsi', 'strategy.entry', 'repainting').
Raw schema
{
"type": "object",
"properties": {
"query": {
"description": "Exact Pine Script term or known concept keyword (e.g., 'ta.rsi', 'strategy.entry', 'repainting').",
"minLength": 1,
"type": "string"
}
},
"required": [
"query"
],
"additionalProperties": false
}
list_prompts
List all available prompts.
Returns JSON with prompt metadata including name, description,
and optional arguments.
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.
Parameters2
name
string
required
The name of the prompt to get
arguments
any
optional
Optional arguments for the prompt
Raw schema
{
"type": "object",
"properties": {
"name": {
"description": "The name of the prompt to get",
"type": "string"
},
"arguments": {
"anyOf": [
{
"additionalProperties": true,
"type": "object"
},
{
"type": "null"
}
],
"default": null,
"description": "Optional arguments for the prompt"
}
},
"required": [
"name"
],
"additionalProperties": false
}
ChatGPT — no config file. In ChatGPT, go to Settings → Connectors → Create and paste https://pinescript-mcp.fly.dev/mcp into the Server URL field. Developer Mode must be enabled (see OpenAI Developer Mode guide).
Claude.ai — add via the web UI's MCP connector settings, not a JSON file.
Version Pinning
Documentation is bundled in the package — each version contains a frozen snapshot. For reproducible agent behaviour, pin to a specific version:
