Instagram Relationship MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INSTAGRAM_MCP_DATA_DIR | No | Absolute local directory for storing browser profile and database. Default: %LOCALAPPDATA%\InstagramRelationshipMcp | |
| INSTAGRAM_MCP_LOG_LEVEL | No | Log level. Default: info, allowed: debug, info, warn, error, silent | |
| INSTAGRAM_MCP_NETWORK_RETRIES | No | Number of retries for network requests. Default: 1, allowed: 0-3 | |
| INSTAGRAM_MCP_RESULT_PAGE_SIZE | No | Default number of results per page. Default: 50, allowed: 1-100 | |
| INSTAGRAM_MCP_CACHE_TTL_MINUTES | No | Cache time-to-live in minutes. Default: 15, allowed: 1-1440 | |
| INSTAGRAM_MCP_FOLLOWING_PAGE_SIZE | No | Number of following items to fetch per page. Default: 12, allowed: 1-200 | |
| INSTAGRAM_MCP_MAX_FOLLOWING_PAGES | No | Maximum number of following pages to fetch. Default: 10000, allowed: 1-100000 | |
| INSTAGRAM_MCP_LOGIN_TIMEOUT_SECONDS | No | Timeout for login in seconds. Default: 300, allowed: 30-1800 | |
| INSTAGRAM_MCP_INTER_REQUEST_DELAY_MS | No | Delay between requests in milliseconds. Default: 250, allowed: 0-10000 | |
| INSTAGRAM_MCP_RELATIONSHIP_BATCH_SIZE | No | Batch size for checking relationship statuses. Default: 12, allowed: 1-200 | |
| INSTAGRAM_MCP_REQUEST_TIMEOUT_SECONDS | No | Timeout for HTTP requests in seconds. Default: 30, allowed: 5-120 | |
| INSTAGRAM_MCP_NAVIGATION_TIMEOUT_SECONDS | No | Timeout for page navigation in seconds. Default: 45, allowed: 5-180 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| instagram_connectA | Use this when the user wants to connect Instagram or resume an unfinished local login. It reuses a verified saved session; otherwise it opens the dedicated local Chromium profile and returns immediately with LOGIN_PENDING. Credentials, 2FA, and challenge responses must be entered only on instagram.com; then use instagram_connection_status. |
| instagram_connection_statusA | Use this when the user wants to check whether Instagram is connected, especially after instagram_connect returned LOGIN_PENDING. It reports the current login or session state and never asks for credentials. |
| instagram_get_non_followersA | Returns accounts the connected user follows that explicitly do not follow the user back. Fetches a complete Following list before classification, reports unknown statuses, caches normalized results locally, and paginates MCP output. |
| instagram_disconnectA | Closes Chromium and permanently deletes the dedicated Instagram browser profile plus locally derived account and relationship data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rankes96-dev/instagram-relationship-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server