campaign_summary — TweetFeed MCP Prompt

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

by client

How to invoke campaign_summary from your client

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

Other prompts on this server

• triage_ioc
• daily_brief

TweetFeed also offers 7 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.