get_outreach_path — Flux LinkedIn MCP MCP Tool Read-only
get_outreach_path
(get outreach path) is one of 67 tools on the
Flux LinkedIn MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_outreach_path from your client
- Claude Code Flux LinkedIn MCP get_outreach_path run in your project directory
- Claude Desktop Flux LinkedIn MCP get_outreach_path ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Flux LinkedIn MCP get_outreach_path ~/.cursor/mcp.json
- VS Code Flux LinkedIn MCP get_outreach_path .vscode/mcp.json
- Zed Flux LinkedIn MCP get_outreach_path ~/.config/zed/settings.json
- Windsurf Flux LinkedIn MCP get_outreach_path ~/.codeium/windsurf/mcp_config.json
- Cline Flux LinkedIn MCP get_outreach_path ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Flux LinkedIn MCP get_outreach_path ~/.gemini/settings.json
- Grok Flux LinkedIn MCP get_outreach_path .mcp.json (in your project root)
- ChatGPT Flux LinkedIn MCP get_outreach_path Settings → Connectors → Advanced → Developer mode
- Claude.ai Flux LinkedIn MCP get_outreach_path Settings → Connectors → Add custom connector
- LangChain Flux LinkedIn MCP get_outreach_path pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http linkedin https://www.fluxgraph.app/mcpOther tools on this server
- list_profiles
- preview_profile
- preview_posting_insights
- preview_search_posts
- claim_preview
- get_posts
- get_profile_summary
- get_posting_insights
- get_topic_insights
- get_engagement_trends
- search_posts
- get_credit_balance
- get_usage_history
- get_cost_estimate
- create_stream
- list_streams
- get_stream_feed
- pause_stream
- resume_stream
- delete_stream
- run_stream_now
- linkedin_profile_info
- linkedin_profile_posts
- linkedin_company_posts
- linkedin_post_search
- linkedin_profile_reactions
- linkedin_profile_comments
- linkedin_job_search
- linkedin_ad_search
- linkedin_people_search
- linkedin_company_search
- linkedin_post_reactions
- linkedin_post_comments
- find_similar_posts
- score_draft
- suggest_angles
- list_segments
- create_segment
- add_to_segment
- remove_from_segment
- resolve_segment
- list_segment_templates
- get_alerts
- create_collection
- add_to_collection
- remove_from_collection
- list_collections
- resolve_collection
- create_campaign
- add_campaign_accounts
- map_constellation
- score_connections
- get_outreach_queue
- get_engagement_brief
- log_outcome
- get_campaign_stats
- save_post
- get_post_engagers_by_company
- get_engagement_industry_breakdown
- get_alumni_engagers
- get_engager_position_history
- get_target_warmth_brief
- traverse_graph_help
- traverse_graph
- get_company_engagement_overlap
- get_post_set_engagers
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.