Post engagement → their network — InstaVision — Instagram niche discovery MCP Resource
Post engagement → their network
is one of 11 resources on the
InstaVision — Instagram niche discovery
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Post engagement → their network from your client
- Claude Code InstaVision — Instagram niche discovery Resource/Post engagement → their network run in your project directory
- Claude Desktop InstaVision — Instagram niche discovery Resource/Post engagement → their network ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor InstaVision — Instagram niche discovery Resource/Post engagement → their network ~/.cursor/mcp.json
- VS Code InstaVision — Instagram niche discovery Resource/Post engagement → their network .vscode/mcp.json
- Zed InstaVision — Instagram niche discovery Resource/Post engagement → their network ~/.config/zed/settings.json
- Windsurf InstaVision — Instagram niche discovery Resource/Post engagement → their network ~/.codeium/windsurf/mcp_config.json
- Cline InstaVision — Instagram niche discovery Resource/Post engagement → their network ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI InstaVision — Instagram niche discovery Resource/Post engagement → their network ~/.gemini/settings.json
- Grok InstaVision — Instagram niche discovery Resource/Post engagement → their network .mcp.json (in your project root)
- ChatGPT InstaVision — Instagram niche discovery Resource/Post engagement → their network Settings → Connectors → Advanced → Developer mode
- Claude.ai InstaVision — Instagram niche discovery Resource/Post engagement → their network Settings → Connectors → Add custom connector
- LangChain InstaVision — Instagram niche discovery Resource/Post engagement → their network pip install langchain-mcp-adapters
Other resources on this server
Read from the server itself, by connecting to it and calling resources/list on 4 October 2026.
A listing does not declare its resources, 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 resource's type and contents.