PineScript MCP Documentation Server
Related Servers
Alternatives to PineScript MCP Documentation Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceMCP server that lets AI agents directly control and interact with the TradingView desktop app via 88 chart-control tools, enabling automated chart reading, Pine Script compilation, strategy optimization, and replay control.411382 npm47MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that extends TradingView with AI-driven morning briefs, trading rule automation, and 81 tools for chart control, Pine Script development, replay practice, and multi-pane layouts.78 npm-
- AlicenseNot gradedqualityAmaintenanceA local MCP server that connects TradingView Desktop to AI assistants via Chrome DevTools Protocol, enabling Pine Script development, multi-timeframe analysis, and Wyckoff scanning with a rules engine.44 npm1MIT
- AlicenseAqualityDmaintenanceProvides comprehensive Pine Script v6 documentation and tools to help AI assistants look up functions, validate syntax, and generate accurate code. It enables linting, version conversion from v5 to v6, and deep conceptual analysis to prevent code hallucinations.109MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that connects AI assistants to TradingView Desktop via Chrome DevTools Protocol, enabling chart analysis, Pine Script development, and workflow automation through natural language.78 npm-
- FlicenseNot gradedqualityBmaintenanceA comprehensive MCP server that integrates TradingView Desktop automation, screener API, Yahoo Finance, IDX/BEI tools, backtesting, news sentiment, trade math, and market sessions. It enables traders to perform technical analysis, backtest strategies, manage positions, and automate TradingView tasks through natural language.-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: service version info, documentation search, code review, and syntax validation. No overlap or ambiguity.
Naming is inconsistent: three tools use 'pinescript_' prefix but one uses 'mcp_service_version', and 'syntax_compatibility_validation' does not follow a verb_noun pattern. Mixed conventions make it harder to predict tool names.
With 4 tools covering distinct aspects of PineScript documentation and validation, the tool count is well-scoped for the server's purpose, not too few or too many.
The set covers reference search, code review, and syntax compatibility, which are core needs. A minor gap is missing a tool for listing specific language features or version history, but overall functional completeness is good.