ticker_activity — trades MCP Prompt

ticker_activity is one of 3 prompts on the trades MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke ticker_activity from your client

• Claude Code trades Prompt/ticker_activity run in your project directory
• Claude Desktop trades Prompt/ticker_activity ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor trades Prompt/ticker_activity ~/.cursor/mcp.json
• VS Code trades Prompt/ticker_activity .vscode/mcp.json
• Zed trades Prompt/ticker_activity ~/.config/zed/settings.json
• Windsurf trades Prompt/ticker_activity ~/.codeium/windsurf/mcp_config.json
• Cline trades Prompt/ticker_activity ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI trades Prompt/ticker_activity ~/.gemini/settings.json
• Grok trades Prompt/ticker_activity .mcp.json (in your project root)
• ChatGPT trades Prompt/ticker_activity Settings → Connectors → Advanced → Developer mode
• Claude.ai trades Prompt/ticker_activity Settings → Connectors → Add custom connector
• LangChain trades Prompt/ticker_activity pip install langchain-mcp-adapters

Other prompts on this server

• conflicts_overview
• person_trades

trades also offers 3 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.