by bob-lance
Unlock Instagram insights to boost advertising and marketing services. Analyze interactions for better IG engagement and
Analyzes Instagram posts and accounts to extract engagement metrics, demographic insights, and identify potential marketing leads through comment and profile analysis.
Instagram Engagement is a community-built MCP server published by bob-lance that provides AI assistants with tools and capabilities via the Model Context Protocol. Unlock Instagram insights to boost advertising and marketing services. Analyze interactions for better IG engagement and It is categorized under search web, analytics data.
You can install Instagram Engagement in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Instagram Engagement is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
Instagram Engagement reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Instagram Engagement for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Useful MCP listing: Instagram Engagement is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Instagram Engagement against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Instagram Engagement is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Instagram Engagement against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Instagram Engagement surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Instagram Engagement is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
According to our notes, Instagram Engagement benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Instagram Engagement has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 27
An MCP server that provides tools for analyzing Instagram engagement metrics, extracting demographic insights, and identifying potential leads from Instagram posts and accounts.
To install Instagram Engagement Analysis for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @Bob-lance/instagram-engagement-mcp --client claude
npm install -g instagram-engagement-mcp
git clone https://github.com/Bob-lance/instagram-engagement-mcp.git
cd instagram-engagement-mcp
npm install
.env.example file to .env and add your Instagram credentials:
cp .env.example .env
.env file with your Instagram username and passwordIf you cloned the repository, build the project:
npm run build
Add the server to your MCP settings file:
{
"mcpServers": {
"instagram-engagement": {
"command": "npx",
"args": ["instagram-engagement-mcp"],
"env": {
"INSTAGRAM_USERNAME": "your_instagram_username",
"INSTAGRAM_PASSWORD": "your_instagram_password"
},
"disabled": false,
"autoApprove": []
}
}
}
If you cloned the repository instead of installing from npm, use:
{
"mcpServers": {
"instagram-engagement": {
"command": "node",
"args": ["/path/to/instagram-engagement-mcp/build/index.js"],
"env": {
"INSTAGRAM_USERNAME": "your_instagram_username",
"INSTAGRAM_PASSWORD": "your_instagram_password"
},
"disabled": false,
"autoApprove": []
}
}
}
Analyze comments on an Instagram post to identify sentiment, themes, and potential leads.
Parameters:
postUrl (required): URL of the Instagram post to analyzemaxComments (optional): Maximum number of comments to analyze (default: 100)Compare engagement metrics across different Instagram accounts.
Parameters:
accounts (required): List of Instagram account handles to comparemetrics (optional): Metrics to compare (default: all)Extract demographic insights from users engaged with a post or account.
Parameters:
accountOrPostUrl (required): Instagram account handle or post URL to analyzesampleSize (optional): Number of users to sample for demographic analysis (default: 50)Identify potential leads based on engagement patterns.
Parameters:
accountOrPostUrl (required): Instagram account handle or post URL to analyzecriteria (optional): Criteria for identifying leadsGenerate a comprehensive engagement report for an Instagram account.
Parameters:
account (required): Instagram account handlestartDate (optional): Start date for the report (YYYY-MM-DD)endDate (optional): End date for the report (YYYY-MM-DD)Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.