Pine Script v6 Documentation MCP Server

by paulieb89 Your server? Claim it

answering

Pine Script v6 Documentation is answering right now. Last checked 4 min ago. 281 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 168 · avg 33 · +61% w/w

a month agotoday

Uptime history 48 days of history · worst day 49%

48 days agonow

50.0%

Uptime 24h

92 of 184 checks

Tools

read from the server

190 ms

Response time

average over 24h

281

Installs / week

npm and PyPI

What the code does

We read the source, 1 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Page executes code built at runtime pinescript-linter-playground.html:1018

  document.getElementById("lineNumbers").innerHTML = html;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 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"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

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	190 ms	4 min ago
https://pinescript-mcp.fly.dev/sse	sse	answering	171 ms	4 min ago

Alternatives to Pine Script v6 Documentation

same job, measured the same way

Metricui

by mpmcgowen

React dashboard components — API lookup, code generation, and prop validation for AI tools.

32 installs/wk local only

Sceneview

by sceneview

3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.

148 installs/wk local only

Sceneview

by thomasgorisse

3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.

local only

SceneView

by sceneview

3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.

local only

Icdwise

by qinisolabs

Verified ICD-10-CM code lookup & validation for AI agents — official descriptions, not guesses.

62 installs/wk local only

Denialbot

by edgeedgehq

Insurance denial code lookup, appeal letter generation, and denial analysis for AI agents.

33 installs/wk local only

Python Code Validator

by jkanselaar

Validates AI-generated Python: syntax, lint, security scan and deterministic repair.

3 tools answering

Mne Docs

by weiyongxu

MCP server for MNE-Python documentation, source code, GitHub issues, and forum

115 installs/wk local only

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 92 of 184 checks got a reply (50.0%), average response time 190 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 190 ms on average, which is faster than 69% 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 281 times in the last week. Week over week that is +61%. 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 9 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.