ipo_pipeline — filingpulse MCP Prompt

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

by client

How to invoke ipo_pipeline from your client

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

Other prompts on this server

• insider_activity
• events_digest

filingpulse also offers 2 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.