Skip to main content
Glama
enesjakozh
duhlink

Instagram MCP Server

by duhlink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

인스타그램 MCP 서버

Chrome의 기존 로그인 세션을 사용하여 Instagram 게시물을 가져오기 위한 MCP(모델 컨텍스트 프로토콜) 서버입니다.

특징

  • 관심사를 명확하게 분리한 모듈식 아키텍처

  • TypeScript를 사용한 유형 안전 구현

  • 향상된 오류 처리 및 로깅

  • 환경 변수를 통해 구성 가능

  • JSON-RPC 2.0 호환 통신

  • 자동 미디어 다운로드 및 메타데이터 생성

  • SEO 친화적인 설명 생성

Related MCP server: instagram-mcp

건축학

서버는 다음과 같은 구조를 가진 모듈형 아키텍처를 따릅니다.

지엑스피1

구성

서버에는 다음과 같은 환경 변수가 필요합니다.

  • 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 프로필에서 최근 게시물을 가져옵니다.

매개변수:

  • 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. 테스트 지원

    • 모듈식 설계로 테스트 가능

    • 종속성 주입 준비 완료

    • 명확한 인터페이스

특허

MIT

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
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

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