Skip to main content
Glama
enesjakozh
duhlink

Instagram MCP Server

by duhlink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Instagram MCP 服务器

使用 Chrome 现有登录会话获取 Instagram 帖子的模型上下文协议 (MCP) 服务器。

特征

  • 具有明确关注点分离的模块化架构

  • 使用 TypeScript 的类型安全实现

  • 改进的错误处理和日志记录

  • 可通过环境变量配置

  • 符合 JSON-RPC 2.0 的通信

  • 自动媒体下载和元数据生成

  • 搜索引擎优化友好的描述生成

Related MCP server: instagram-mcp

建筑学

该服务器采用模块化架构，结构如下：

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

配置

服务器需要以下环境变量：

  • CHROME_USER_DATA_DIR ：包含登录会话的 Chrome 用户数据目录的路径

可以通过配置管理器获得其他配置选项：

  • 浏览器设置（视口、超时）

  • Instagram 设置（延迟、批量大小）

  • 保存目录和文件路径

用法

  1. 安装依赖项：

    npm install

  2. 构建服务器：

    npm run build

  3. 运行服务器：

    CHROME_USER_DATA_DIR=/path/to/chrome/profile npm start

可用工具

获取 Instagram 帖子

从 Instagram 个人资料中获取最近的帖子。

参数：

  • username （必填）：用于获取帖子的 Instagram 用户名

  • limit （可选）：要获取的帖子数量（1-50）或“全部”

  • saveDir （可选）：保存媒体文件和元数据的目录

  • delayBetweenPosts （可选）：处理帖子之间等待的毫秒数

例子：

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "call_tool",
  "params": {
    "name": "get_instagram_posts",
    "arguments": {
      "username": "example",
      "limit": 10
    }
  }
}

错误处理

服务器使用标准化的错误代码和消息：

  • INVALID_REQUEST ：请求格式或参数无效

  • INVALID_PARAMS ：缺少参数或参数无效

  • METHOD_NOT_FOUND ：未知方法或工具

  • INTERNAL_ERROR ：服务器端错误

发展

  1. 以开发模式启动：

    npm run dev

  2. 运行 linter：

    npm run lint

比原版有所改进

  1. 模块化架构

    • 清晰的关注点分离

    • 更好的代码组织

    • 更易于维护和扩展

  2. 类型安全

    • 全面的 TypeScript 类型

    • 更好的错误捕获

    • 改进的 IDE 支持

  3. 错误处理

    • 标准化错误代码

    • 更好的错误消息

    • 适当的错误传播

  4. 配置

    • 集中配置

    • 环境变量验证

    • 类型安全的配置访问

  5. 代码质量

    • 一致的编码风格

    • 更好的文档

    • 改进的日志记录

  6. 测试支持

    • 模块化设计支持测试

    • 依赖注入准备就绪

    • 清晰的界面

执照

麻省理工学院

Available Tools

1 tool
get_instagram_postsC

Get recent posts from an Instagram profile using existing Chrome login

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of posts to fetch (1-3) or "all" for continuous batches
startFromNoIndex to start fetching from (for pagination)
usernameYesInstagram username to fetch posts from

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only mentions 'using existing Chrome login' as a behavioral trait, hinting at authentication needs. It fails to disclose critical behaviors like rate limits, pagination mechanics (implied by 'startFrom' but not explained), error handling, or what 'recent' means temporally, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core action and key constraint ('using existing Chrome login'). It's front-loaded with the main purpose, though it could be slightly more structured by separating functional from implementation details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete for a tool with 3 parameters and behavioral complexity. It lacks details on return values (e.g., post format, errors), authentication specifics, or operational limits, making it inadequate for full agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents parameters like 'limit' and 'startFrom'. The description adds no additional meaning beyond what's in the schema, such as clarifying 'recent' in relation to parameters or usage context, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get recent posts') and target resource ('from an Instagram profile'), making the purpose understandable. However, it doesn't differentiate from siblings (none exist), and the phrase 'using existing Chrome login' adds implementation detail rather than clarifying the core purpose, slightly reducing specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints beyond the implied need for Chrome login. With no siblings, differentiation isn't needed, but it lacks context like when to fetch posts (e.g., for monitoring, analysis) or any exclusions, leaving usage unclear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedget_instagram_posts
Deploy Server
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving Instagram posts, leaving no room for misselection.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (get_instagram_posts), which is consistent and predictable. Since there is only one tool, naming consistency is inherently perfect.

Tool Count2/5

One tool is too few for a server labeled 'Instagram MCP Server', which implies broader Instagram functionality. This minimal toolset feels thin and under-scoped for the apparent domain, limiting agent capabilities.

Completeness2/5

The tool surface is severely incomplete for Instagram operations. It only allows retrieving posts, with no coverage for actions like posting, commenting, liking, or managing profiles, leading to significant gaps that will cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches