Pine Script v6 Documentation MCP Server

io.github.paulieb89/pinescript-mcp

answering

Pine Script v6 Documentation is answering right now. Last checked 9 min ago. 179 installs a week from pypi. It exposes 10 tools. Last commit 17 Jul 2026.

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

Installs per day peak 115 · avg 36 · -31% w/w

a month agotoday

Uptime history 45 hours of history · worst hour 33%

45 hours agonow

48.9%

Uptime 24h

89 of 182 checks

Tools

read from the server

204 ms

Response time

average over 24h

179

Installs / week

npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.pinescript-mcp]
url = "https://pinescript-mcp.fly.dev/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

docs

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, collections.md, drawing.md, general.md). Data sourced from bundled Pine Script v6 documentation.

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 full. Data sourced from bundled Pine Script v6 documentation.

doc

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 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.

functions

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 read its documentation. Data sourced from bundled pine_v6_functions.json.

prompt

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.

prompts

list_prompts

List all available prompts. Returns JSON with prompt metadata including name, description, and optional arguments.

resolve

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() + get_section() for large files. For natural language questions use search_docs() instead. Data sourced from bundled TOPIC_MAP and doc file content scan.

section

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.

sections

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 documentation.

validate

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 functions in the relevant namespace if the function is invalid. Data sourced from bundled pine_v6_functions.json.

Endpoints

URL	Transport	State	Latency	Checked
https://pinescript-mcp.fly.dev/mcp	streamable-http	answering	170 ms	9 min ago
https://pinescript-mcp.fly.dev/sse	sse	answering	471 ms	9 min ago

Pine Script v6 Documentation — questions

Answers built from our own checks of this server.

What can Pine Script v6 Documentation do?

It exposes 10 tools, read directly from the server on our last check. Among them: get_doc, get_functions, get_prompt, get_section, list_docs, list_prompts and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Pine Script v6 Documentation working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 182 checks got a reply (48.9%), average response time 204 ms. The bar chart above shows every period we have measured.

How do I connect Pine Script v6 Documentation?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Pine Script v6 Documentation need an API key?

No. Pine Script v6 Documentation completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Pine Script v6 Documentation?

It answers our handshake in 204 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Pine Script v6 Documentation?

The pypi package pinescript-mcp was installed 179 times in the last week. Week over week that is -31%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Pine Script v6 Documentation open source?

Yes — it is published under the MIT licence, written in Python and 7 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.