pinescript-mcp 0.1.0__tar.gz

pinescript_mcp-0.1.0/.gitignore

@@ -0,0 +1,222 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.tv_auth_state.json
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# Project-specific
+research/output/
+.python-version
+uv.lock

pinescript_mcp-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 bch
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pinescript_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,121 @@
+Metadata-Version: 2.4
+Name: pinescript-mcp
+Version: 0.1.0
+Summary: MCP server providing Pine Script v6 documentation for AI assistants
+Project-URL: Homepage, https://github.com/bch/pinescript-mcp
+Project-URL: Documentation, https://github.com/bch/pinescript-mcp#readme
+Project-URL: Repository, https://github.com/bch/pinescript-mcp
+Author: bch
+License-Expression: MIT
+License-File: LICENSE
+Keywords: ai,claude,documentation,mcp,pine-script,tradingview
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Documentation
+Requires-Python: >=3.10
+Requires-Dist: mcp>=1.26.0
+Description-Content-Type: text/markdown
+
+# 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
+
+## Installation
+
+```bash
+pip install pinescript-mcp
+```
+
+## Usage with Claude Desktop
+
+Add to `~/.config/claude/claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "pinescript-docs": {
+      "command": "pinescript-mcp"
+    }
+  }
+}
+```
+
+## Usage with Claude Code
+
+Add to `.mcp.json` in your project:
+
+```json
+{
+  "mcpServers": {
+    "pinescript-docs": {
+      "type": "stdio",
+      "command": "pinescript-mcp"
+    }
+  }
+}
+```
+
+## Available Tools
+
+| Tool | Description |
+|------|-------------|
+| `list_docs()` | List all documentation files with descriptions |
+| `get_doc(path)` | Read a specific documentation file |
+| `search_docs(query)` | Full-text search across all docs |
+| `get_functions(namespace)` | List valid functions (ta, strategy, etc.) |
+| `validate_function(name)` | Check if a function exists in Pine v6 |
+| `resolve_topic(query)` | Map a question to relevant docs |
+| `get_manifest()` | Get routing guidance for topics |
+
+## 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.supertrend` doesn't exist)
+- Deprecated syntax from v4/v5
+- Incorrect parameter orders
+- Missing required arguments
+
+## Development
+
+```bash
+# Clone and install locally
+git clone https://github.com/bch/pinescript-mcp
+cd pinescript-mcp
+pip install -e .
+
+# Run the server
+pinescript-mcp
+```
+
+## License
+
+MIT

pinescript_mcp-0.1.0/README.md

@@ -0,0 +1,98 @@
+# 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
+
+## Installation
+
+```bash
+pip install pinescript-mcp
+```
+
+## Usage with Claude Desktop
+
+Add to `~/.config/claude/claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "pinescript-docs": {
+      "command": "pinescript-mcp"
+    }
+  }
+}
+```
+
+## Usage with Claude Code
+
+Add to `.mcp.json` in your project:
+
+```json
+{
+  "mcpServers": {
+    "pinescript-docs": {
+      "type": "stdio",
+      "command": "pinescript-mcp"
+    }
+  }
+}
+```
+
+## Available Tools
+
+| Tool | Description |
+|------|-------------|
+| `list_docs()` | List all documentation files with descriptions |
+| `get_doc(path)` | Read a specific documentation file |
+| `search_docs(query)` | Full-text search across all docs |
+| `get_functions(namespace)` | List valid functions (ta, strategy, etc.) |
+| `validate_function(name)` | Check if a function exists in Pine v6 |
+| `resolve_topic(query)` | Map a question to relevant docs |
+| `get_manifest()` | Get routing guidance for topics |
+
+## 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.supertrend` doesn't exist)
+- Deprecated syntax from v4/v5
+- Incorrect parameter orders
+- Missing required arguments
+
+## Development
+
+```bash
+# Clone and install locally
+git clone https://github.com/bch/pinescript-mcp
+cd pinescript-mcp
+pip install -e .
+
+# Run the server
+pinescript-mcp
+```
+
+## License
+
+MIT

pinescript_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,44 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "pinescript-mcp"
+version = "0.1.0"
+description = "MCP server providing Pine Script v6 documentation for AI assistants"
+readme = "README.md"
+license = "MIT"
+requires-python = ">=3.10"
+authors = [{ name = "bch" }]
+keywords = ["mcp", "pine-script", "tradingview", "documentation", "ai", "claude"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Documentation",
+]
+dependencies = [
+    "mcp>=1.26.0",
+]
+
+[project.urls]
+Homepage = "https://github.com/bch/pinescript-mcp"
+Documentation = "https://github.com/bch/pinescript-mcp#readme"
+Repository = "https://github.com/bch/pinescript-mcp"
+
+[project.scripts]
+pinescript-mcp = "pinescript_mcp.server:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/pinescript_mcp"]
+
+[tool.hatch.build.targets.sdist]
+include = [
+    "src/pinescript_mcp/**/*.py",
+    "src/pinescript_mcp/**/*.md",
+    "src/pinescript_mcp/**/*.json",
+]

pinescript_mcp-0.1.0/src/pinescript_mcp/__init__.py

@@ -0,0 +1,7 @@
+"""Pine Script v6 Documentation MCP Server.
+
+Provides tools to list, search, and read Pine Script v6 documentation
+for use with AI assistants like Claude.
+"""
+
+__version__ = "0.1.0"

pinescript_mcp-0.1.0/src/pinescript_mcp/__main__.py

@@ -0,0 +1,6 @@
+"""Entry point for python -m pinescript_mcp."""
+
+from .server import main
+
+if __name__ == "__main__":
+    main()

pinescript_mcp-0.1.0/src/pinescript_mcp/docs/LLM_MANIFEST.md

@@ -0,0 +1,96 @@
+# Pine Script v6 Documentation Manifest
+
+**Purpose:** This file acts as a directory map for Large Language Models (LLMs). Use this manifest to determine which specific documentation files to retrieve based on the user's request.
+
+**Protocol:** 1.  Identify the user's intent (e.g., "Drawing a line", "Calculating RSI", "Backtesting").
+2.  Locate the relevant file path below.
+3.  Retrieve ONLY that file to conserve context window.
+
+## 1. Syntax and Core Concepts
+
+*Use these files when the user asks about language mechanics, execution flow, or type errors.*
+
+* **`concepts/execution_model.md`**
+  * **Content:** How the script executes bar-by-bar, historical vs. real-time context, and the `var` keyword.
+  * **Keywords:** `barstate`, `history`, `realtime`, `calc_on_every_tick`, `var`, `varip`.
+
+* **`concepts/timeframes.md`**
+  * **Content:** Handling multi-timeframe data and preventing repainting.
+  * **Keywords:** `request.security`, `timeframe.period`, `repainting`, `HTF`.
+
+* **`concepts/colors_and_display.md`**
+  * **Content:** Defining colors, gradients, and transparency.
+  * **Keywords:** `color.new`, `color.from_gradient`, `bgcolor`.
+
+* **`concepts/common_errors.md`**
+  * **Content:** Explanations for common runtime and compile-time errors.
+  * **Keywords:** "Series string", "Undeclared identifier", "max_bars_back".
+
+* **`reference/pine_v6_cheatsheet.md`**
+  * **Content:** Compact reference of ALL valid v6 functions, namespaces, built-in variables, constants, and common pitfalls. Always include this file.
+  * **Keywords:** `cheatsheet`, `valid functions`, `namespaces`, `v6 reference`, `validation`.
+
+## 2. API Reference (The Dictionary)
+
+*Use these files for looking up built-in variables, constants, and keywords.*
+
+* **`reference/variables.md`**
+  * **Content:** Built-in read-only variables regarding the bar, symbol, or status.
+  * **Keywords:** `open`, `high`, `low`, `close`, `volume`, `time`, `syminfo.ticker`, `timeframe.multiplier`, `bar_index`.
+
+* **`reference/constants.md`**
+  * **Content:** Fixed constants used as arguments for functions.
+  * **Keywords:** `color.red`, `shape.triangle`, `plot.style_line`, `size.small`, `alert.freq_once_per_bar`.
+
+* **`reference/types.md`**
+  * **Content:** Data type definitions and type-casting functions.
+  * **Keywords:** `int`, `float`, `bool`, `color`, `string`, `line`, `label`, `box`, `simple`, `series`, `input`.
+
+* **`reference/keywords.md`**
+  * **Content:** Language keywords and control structures.
+  * **Keywords:** `if`, `else`, `switch`, `for`, `while`, `export`, `import`, `method`.
+
+## 3. Function Reference (By Namespace)
+
+*Use these files to find syntax for specific function calls.*
+
+* **`reference/functions/ta.md` (Technical Analysis)**
+  * **Content:** Math for indicators and signal generation.
+  * **Keywords:** `ta.rsi`, `ta.sma`, `ta.ema`, `ta.macd`, `ta.crossover`, `ta.lowest`, `ta.highest`, `ta.pivot`.
+
+* **`reference/functions/strategy.md` (Backtesting)**
+  * **Content:** Strategy testing engine, orders, and trade management.
+  * **Keywords:** `strategy.entry`, `strategy.close`, `strategy.exit`, `strategy.position_size`, `strategy.equity`, `strategy.risk`.
+
+* **`reference/functions/request.md` (External Data)**
+  * **Content:** Requesting data from other symbols, financial data, or seeds.
+  * **Keywords:** `request.security`, `request.financial`, `request.seed`, `request.currency_rate`.
+
+* **`reference/functions/drawing.md` (Visuals)**
+  * **Content:** Plotting data on the chart and drawing geometric shapes.
+  * **Keywords:** `plot`, `plotshape`, `plotchar`, `line.new`, `box.new`, `label.new`, `polyline.new`, `fill`.
+
+* **`reference/functions/collections.md` (Arrays, Maps, Matrices)**
+  * **Content:** Advanced data structures for complex logic.
+  * **Keywords:** `array.new`, `array.push`, `matrix.new`, `matrix.mult`, `map.new`, `map.put`.
+
+* **`reference/functions/general.md` (Math, Strings, Inputs)**
+  * **Content:** Core math, string manipulation, and user inputs.
+  * **Keywords:** `math.abs`, `math.round`, `str.tostring`, `str.format`, `input.int`, `input.bool`, `alert()`.
+
+## 🧭 Routing Logic for LLMs
+
+* **IF** user asks "Write an RSI indicator":
+  * retrieve `reference/functions/ta.md` (for RSI math)
+  * retrieve `reference/functions/drawing.md` (for `plot` and `hline`)
+
+* **IF** user asks "Create a moving average crossover strategy":
+  * retrieve `reference/functions/ta.md` (for `ta.crossover`)
+  * retrieve `reference/functions/strategy.md` (for `strategy.entry`)
+
+* **IF** user asks "Draw a box around the high and low of the last 10 bars":
+  * retrieve `reference/functions/drawing.md` (for `box.new`)
+  * retrieve `reference/functions/ta.md` (for `ta.highest`, `ta.lowest`)
+
+* **IF** user asks "Why is my variable resetting every bar?":
+  * retrieve `concepts/execution_model.md` (check `var` usage)