TradingView Alerts MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TV_ECUID | Yes | Your tv_ecuid cookie value from TradingView. | |
| TV_DEVICE_T | Yes | Your device_t cookie value from TradingView. | |
| TV_USERNAME | Yes | Your TradingView username exactly as it appears on your profile. | |
| TV_SESSIONID | Yes | Your sessionid cookie value from TradingView. | |
| TV_SESSIONID_SIGN | Yes | Your sessionid_sign cookie value from TradingView. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_alertsA | List TradingView alerts on the authenticated account, with their status (active or paused), symbol, timeframe and alert_id. Start here: every other tool targets alerts by the alert_id this returns. Supports filtering by symbol, name or status. |
| create_strategy_alertA | Create a new TradingView alert from one of your saved Pine strategies. Resolves the symbol and its currency-id automatically, and reads the strategy's own default input values so the alert actually fires. Optionally set a webhook URL to forward signals to your own trading bot or endpoint. |
| pause_alertsA | Pause (stop) one or more TradingView alerts. Paused alerts stay on your account but stop firing, and can be reactivated with resume_alerts. Target by alert_ids, or by symbol / name / status filter. |
| resume_alertsA | Resume (restart) previously paused TradingView alerts so they fire again. Target by alert_ids, or by symbol / name / status filter. |
| delete_alertsA | Permanently delete TradingView alerts. This cannot be undone. TradingView has no edit endpoint, so changing an alert means deleting it and creating a replacement. To stop an alert temporarily, use pause_alerts instead. |
| list_saved_strategiesA | List the Pine scripts saved on your TradingView account, flagging which are strategies. Only strategies can drive a strategy alert. Use this to find the exact name to pass to create_strategy_alert. |
| list_alert_firesA | Show the firing history for your alerts: what triggered, and when. |
| resolve_symbolA | Resolve an EXCHANGE:TICKER into TradingView's canonical symbol plus its currency-id, which alerts require. Useful for checking a symbol exists before creating an alert. |
| check_authA | Verify the TradingView session is valid and report the account and alert counts. Run this first if anything returns an authorization error. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/daviddme/tradingview-alerts-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server