PineScript MCP Documentation Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pinescript_referenceA | Search PineScript documentation with enhanced semantic matching and streaming support for large result sets. |
| pinescript_reviewA | Review PineScript code against style guide and language rules. Supports single files, directories, and streaming for large results via JSON chunks. |
| syntax_compatibility_validationA | Validate Pine Script code for v6 syntax compatibility and migration requirements. |
| mcp_service_versionA | Get authoritative version information from package.json plus deployment diagnostics including build status, git commit, and bug fix resolution status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.