pinescript-mcp
MCP server providing Pine Script v6 documentation for AI assistants (Claude, etc.).
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
Quick Start (stdio)
Works with Claude Code, Claude Desktop, Gemini CLI, and any MCP client that supports stdio:
{
"mcpServers": {
"pinescript-docs": {
"type": "stdio",
"command": "uvx",
"args": ["pinescript-mcp"]
}
}
}
Public Server (No Install Required)
No Python or uvx needed — connect directly to the hosted server.
Streamable HTTP — Claude Code, mcpServers with type field):
{
"mcpServers": {
"pinescript-docs": {
"type": "http",
"url": "https://pinescript-mcp.fly.dev/mcp"
}
}
}
Windsurf — uses its own shape (see Windsurf docs). Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"pinescript-docs": {
"serverUrl": "https://pinescript-mcp.fly.dev/mcp"
}
}
}
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:
{
"mcpServers": {
"pinescript-docs": {
"command": "uvx",
"args": ["pinescript-mcp==0.7.5"]
}
}
}
Without pinning, uvx pinescript-mcp gets the latest version.
Available Tools
| Tool | Description |
|---|---|
resolve_topic(query) |
Fast lookup for exact API terms (ta.rsi, repainting) |
search_docs(query) |
Grep for exact strings across all docs |
list_docs() |
List all documentation files with descriptions |
list_sections(path) |
List ## headers in a doc file (for navigating large files) |
get_doc(path) |
Read a specific documentation file |
get_section(path, header) |
Read a specific section by header |
get_functions(namespace) |
List valid functions (ta, strategy, etc.) |
validate_function(name) |
Check if a function exists in Pine v6 |
list_resources() |
Browse available documentation resources |
read_resource(uri) |
Read a doc resource by URI (e.g. docs://manifest) |
list_prompts() |
List available prompt templates |
get_prompt(name, arguments) |
Render a prompt template with arguments |
Available Prompts
| Prompt | Description |
|---|---|
debug_error(error, code) |
Analyze a Pine Script compilation error |
convert_v5_to_v6(code) |
Convert Pine Script v5 code to v6 syntax |
explain_function(name) |
Explain a Pine Script function in detail |
Available Resources
| URI | Description |
|---|---|
docs://manifest |
Start here — routing guide for Pine Script questions |
docs://functions |
Complete Pine Script v6 function list (JSON) |
docs://{path} |
Any doc file by path (e.g. concepts/timeframes.md) |
Example Queries
- "How do I create a trailing stop in Pine Script?"
- "What's the difference between var and varip?"
- "Is ta.supertrend a valid function?"
- "How do I avoid repainting with request.security?"
Documentation Coverage
The server bundles comprehensive Pine Script v6 documentation:
- Concepts: Execution model, timeframes, colors, methods, objects, common errors
- Reference: Types, variables, constants, keywords, operators, annotations
- Functions: Technical analysis (ta.*), strategies, requests, drawings, collections
- Visuals: Plots, fills, shapes, tables, lines, boxes, backgrounds
- Writing Scripts: Style guide, debugging, optimization, limitations
Why Use This?
AI models often hallucinate Pine Script functions or use deprecated v5 syntax. This MCP server grounds the AI in actual v6 documentation, preventing:
- Made-up function names (e.g.,
ta.hulldoesn't exist, useta.hma) - Deprecated syntax from v4/v5
- Incorrect parameter orders
- Missing required arguments
Skills
Combine with skills for even more control available at bouch.dev/products/pine-strategy-builder.
Development
# Clone and install locally
git clone https://github.com/paulieb89/pinescript-mcp
cd pinescript-mcp
pip install -e .
# Run the server
pinescript-mcp
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for pinescript-mcp 0.7.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pinescript_mcp-0.7.5.tar.gz | 324.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pinescript_mcp-0.7.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 676.8 kB
Release files / pinescript_mcp-0.7.5.tar.gz
| Download URL | pinescript_mcp-0.7.5.tar.gz |
|---|---|
| Size | 324.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6f499b769bbed16f55aa517d4b1d322a1a0deee17f88b6130243b1f97fcdbeb
|
|
BLAKE2b-256 checksum How to use checksums |
99598c80237d867fa392e1d6f8eac45d13088f0a7a5d56b7c8cda1c7196ac416
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 17, 2026.
Transparency logRelease files / pinescript_mcp-0.7.5-py3-none-any.whl
| Download URL | pinescript_mcp-0.7.5-py3-none-any.whl |
|---|---|
| Size | 352.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d08cd96af8716b0a5becb574346a8d845718a24d2062fa838f377aa8bccc12d
|
|
BLAKE2b-256 checksum How to use checksums |
bb7b5c270b4d6bd5c3536950e0037f3a20082d0ea6950a5ea420f30f979c9a69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 17, 2026.
Transparency log
