- Home
- MCP servers
- Pine Script v6
Pine Script v6
- javascript
0
GitHub Stars
javascript
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"harunamitrader-pinescriptv6_mcp": {
"command": "node",
"args": [
"server.mjs",
"--manual",
"./manual.json"
],
"env": {
"PINE_MANUAL_PATH": "./manual.json"
}
}
}
}You have a lightweight, read-only MCP server that uses a prebuilt Pine Script v6 reference (manual.json) to provide fast, structured access for code completion, search, and entry details. It runs locally in stdio mode and is designed to help you craft accurate Pine Script code with reliable, verifiable information.
How to use
Interact with the MCP server through your preferred MCP client by querying for symbols, getting entry details, and completing prefixes. You can perform cross-searches to discover functions, constants, and annotations, request detailed information for a specific entry by id, obtain immediate symbol completions from a namespace or prefix, and get a broad overview of available categories to guide your exploration.
How to install
Prerequisites: Node.js must be installed on your system.
Clone the project and navigate to the MCP component directory.
git clone https://github.com/harunamitrader/pinescriptV6_MCP.git
cd pinescriptV6_MCP/pinescriptMCP
Install dependencies to prepare the MCP server for use.
npm i
Start the MCP server using the included manual JSON. The server loads the manual.json at startup and builds a lightweight index in memory.
node server.mjs --manual ./manual.json
If you need to point to a different manual.json path
node server.mjs --manual C:/path/to/manual.json
## Configuration and notes
Environment variable you can set to specify a manual path (alternative to passing --manual) is PINE\_MANUAL\_PATH.
PINE_MANUAL_PATH=C:/path/to/manual.json node server.mjs
## Examples of common usage patterns
- Search for a term across functions, constants, and annotations with a fuzzy query.
- Get the minimum details for a specific entry by id to verify its title, kind, and source information.
- Complete a symbol prefix such as ta. or color. to retrieve namespace-aware suggestions.
- List category counts to understand the scope of available documentation (annotation, const, function, type).
## Security and access
This server is read-only and does not perform external writes or calls. Ensure your client's network access complies with your security requirements.
## Available tools
### search\_docs
Cross-search functions, constants, and annotations by query with optional kind filtering to broaden or narrow results.
### get\_entry
Retrieve a single entry by id with minimal, structured details suitable for LLNC consumption.
### complete\_symbol
Provide prefix-based symbol completions within a namespace, enabling fast, low-overhead coding assistance.
### list\_categories
Return a summary of the number of entries per category (annotation, const, function, type) to understand the scope of documentation.