daily_market_briefing — PreReason MCP Prompt
daily_market_briefing
is one of 6 prompts on the
PreReason
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke daily_market_briefing from your client
- Claude Code PreReason Prompt/daily_market_briefing run in your project directory
- Claude Desktop PreReason Prompt/daily_market_briefing ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PreReason Prompt/daily_market_briefing ~/.cursor/mcp.json
- VS Code PreReason Prompt/daily_market_briefing .vscode/mcp.json
- Zed PreReason Prompt/daily_market_briefing ~/.config/zed/settings.json
- Windsurf PreReason Prompt/daily_market_briefing ~/.codeium/windsurf/mcp_config.json
- Cline PreReason Prompt/daily_market_briefing ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PreReason Prompt/daily_market_briefing ~/.gemini/settings.json
- Grok PreReason Prompt/daily_market_briefing .mcp.json (in your project root)
- ChatGPT PreReason Prompt/daily_market_briefing Settings → Connectors → Advanced → Developer mode
- Claude.ai PreReason Prompt/daily_market_briefing Settings → Connectors → Add custom connector
- LangChain PreReason Prompt/daily_market_briefing pip install langchain-mcp-adapters
Other prompts on this server
PreReason 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.