Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"instagram-server-next-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for fetching Instagram posts using Chrome's existing login session.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication / marketing
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
DataForSEO API modelcontextprotocol server
An MCP server that securely interfaces with your iMessage database via the Model Context Protocol (MCP), allowing LLMs to query and analyze iMessage conversations. It includes robust phone number validation, attachment processing, contact management, group chat handling, and full support for sending and receiving messages.
MCP server for Kaseya Autotask PSA — 39 tools for companies, tickets, projects, time entries, and more
MCP Security Weekly
Get CVE alerts and security updates for Instagram Server Next Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for fetching Instagram posts using Chrome's existing login session.
The server follows a modular architecture with the following structure:
src/
├── core/ # Core MCP functionality
│ ├── mcp/ # MCP server implementation
│ │ ├── server.ts # Server class
│ │ ├── stdio.ts # StdioServerTransport
│ │ └── index.ts # Barrel exports
│ ├── types/ # Core type definitions
│ │ └── mcp.ts # MCP types
│ └── utils/ # Utility functions
│ ├── config.ts # Configuration management
│ └── errors.ts # Error handling
├── features/ # Feature modules
│ └── instagram/ # Instagram feature
│ ├── types.ts # Instagram types
│ ├── utils/ # Feature utilities
│ │ ├── media.ts # Media handling
│ │ ├── post.ts # Post processing
│ │ └── seo.ts # SEO generation
│ └── instagram.service.ts # Instagram service
├── services/ # Shared services
│ └── browser/ # Browser service
│ ├── types.ts # Browser types
│ └── browser.service.ts # Browser service
├── index.ts # Entry point
└── server.ts # Main server class
The server requires the following environment variables:
CHROME_USER_DATA_DIR: Path to Chrome user data directory containing login sessionAdditional configuration options are available through the config manager:
Install dependencies:
npm install
Build the server:
npm run build
Run the server:
CHROME_USER_DATA_DIR=/path/to/chrome/profile npm start
Fetches recent posts from an Instagram profile.
Parameters:
username (required): Instagram username to fetch posts fromlimit (optional): Number of posts to fetch (1-50) or "all"saveDir (optional): Directory to save media files and metadatadelayBetweenPosts (optional): Milliseconds to wait between processing postsExample:
{
"jsonrpc": "2.0",
"id": 1,
"method": "call_tool",
"params": {
"name": "get_instagram_posts",
"arguments": {
"username": "example",
"limit": 10
}
}
}
The server uses standardized error codes and messages:
INVALID_REQUEST: Invalid request format or parametersINVALID_PARAMS: Missing or invalid parametersMETHOD_NOT_FOUND: Unknown method or toolINTERNAL_ERROR: Server-side errorsStart in development mode:
npm run dev
Run linter:
npm run lint
Modular Architecture
Type Safety
Error Handling
Configuration
Code Quality
Testing Support