Skip to main content
Glama
HikerAPI — Instagram MCP

HikerAPI — Instagram MCP

hikerapi-mcp

npm version npm downloads License: MIT

MCP-сервер для HikerAPI — API данных Instagram. Доступен в npm: hikerapi-mcp.

Автоматически генерирует инструменты MCP из спецификации HikerAPI OpenAPI при запуске, поэтому каждый не устаревший эндпоинт GET доступен без написания оберток вручную. HikerAPI предоставляет только эндпоинты для чтения (GET) — сервер сопоставляет каждый из них 1:1 с инструментом MCP (GET /v2/user/by/username → get_v2_user_by_username).

Получите 100 бесплатных запросов к API

Зарегистрируйтесь по этой ссылке и получите 100 бесплатных запросов к HikerAPI — кредитная карта не требуется. Этого достаточно, чтобы подключить MCP-сервер, попробовать несколько промптов в Claude/Cursor/Codex и оценить качество данных перед покупкой.

Получите свои 100 бесплатных запросов здесь

Related MCP server: DataLikers — Instagram & TikTok MCP

Быстрый старт

  1. Получите API-ключ на hikerapi.com/tokens.

  2. Добавьте сервер в своего ИИ-ассистента.

  3. Спросите ассистента о чем-то вроде:

    • "Получи профиль Instagram для @nasa."

    • "Найди 5 последних публикаций по хэштегу #photography."

    • "Покажи истории пользователя с id 25025320."

Claude Code

claude mcp add hikerapi -e HIKERAPI_KEY=your-api-key -- npx -y hikerapi-mcp

Claude Desktop

Добавьте в claude_desktop_config.json:

{
  "mcpServers": {
    "hikerapi": {
      "command": "npx",
      "args": ["-y", "hikerapi-mcp"],
      "env": {
        "HIKERAPI_KEY": "your-api-key"
      }
    }
  }
}

Cursor / Windsurf

Аналогично Claude Desktop — поместите блок в раздел mcpServers в файле конфигурации MCP приложения.

Zed

Добавьте в ~/.config/zed/settings.json:

{
  "context_servers": {
    "hikerapi": {
      "command": "npx",
      "args": ["-y", "hikerapi-mcp"],
      "env": {
        "HIKERAPI_KEY": "your-api-key"
      }
    }
  }
}

OpenAI Codex

Добавьте в ~/.codex/config.toml:

[mcp_servers.hikerapi]
command = "npx"
args = ["-y", "hikerapi-mcp"]

[mcp_servers.hikerapi.env]
HIKERAPI_KEY = "your-api-key"

Инструменты

Инструменты генерируются при запуске из актуальной спецификации HikerAPI OpenAPI, поэтому список всегда соответствует текущему API. Примерно 100+ инструментов в следующих группах (количество на момент написания):

Группа

Инструменты

Примеры

Профиль пользователя

36

get_v2_user_by_username, get_v2_user_by_id, get_v1_user_medias

Детали публикации

20

get_v2_media_info_by_code, get_v2_media_comments, get_v2_media_likers

Поиск

13

get_v1_search_users, get_v1_search_hashtags

Хэштеги

7

get_v2_hashtag_medias_top, get_v2_hashtag_medias_recent

Истории

7

get_v2_story_by_url, get_v1_story_by_id

Локация

7

get_v1_location_medias_recent, get_v1_location_search

Аудио, Репосты, Актуальное, Комментарии

~10

get_v2_track_by_id, get_v1_share_by_url, …

Название каждого инструмента повторяет его эндпоинт (GET /v2/user/by/username → get_v2_user_by_username). Ваш ассистент может вызвать tools/list через MCP, чтобы получить полный актуальный список со схемами параметров. Группы Legacy и System исключены по умолчанию.

Конфигурация

Переменная

Описание

Обязательно

HIKERAPI_KEY

Ваш ключ доступа HikerAPI (отправляется в заголовке x-access-key)

да

HIKERAPI_URL

Базовый URL. По умолчанию: https://api.hikerapi.com (псевдоним https://api.instagrapi.com)

нет

HIKERAPI_SPEC_URL

URL спецификации OpenAPI. По умолчанию: ${HIKERAPI_URL}/openapi.json

нет

HIKERAPI_TAGS

Белый список: включать только операции с этими тегами (через запятую)

нет

HIKERAPI_EXCLUDE_TAGS

Черный список: дополнительные теги для исключения (помимо стандартных Legacy,System)

нет

HIKERAPI_TIMEOUT_MS

Тайм-аут для каждого запроса к API. По умолчанию: 30000

нет

HIKERAPI_SPEC_TIMEOUT_MS

Тайм-аут для получения спецификации при запуске. По умолчанию: 60000

нет

HIKERAPI_MAX_RESPONSE_BYTES

Максимальное количество байт, считываемое из каждого ответа API. По умолчанию: 10485760 (10 МБ)

нет

HIKERAPI_MAX_SPEC_BYTES

Максимальное количество байт, считываемое из спецификации OpenAPI. По умолчанию: 8388608 (8 МБ)

нет

Теги Legacy и System исключены по умолчанию. Устаревшие операции также пропускаются.

Если HIKERAPI_URL указывает на хост, отличный от api.hikerapi.com или api.instagrapi.com, сервер выведет предупреждение при запуске — ваш ключ будет отправлен туда, поэтому используйте это только для собственного или проксированного HikerAPI.

Пример — открыть только самые популярные группы:

"env": {
  "HIKERAPI_KEY": "...",
  "HIKERAPI_TAGS": "User Profile,Post Details,Search,Hashtags,Stories"
}

Как это работает

AI Assistant ←stdio→ hikerapi-mcp ──https──> api.hikerapi.com
                          │
                          └─ fetches /openapi.json once on startup,
                             builds one MCP tool per GET endpoint

Аргументы инструментов сопоставляются с параметрами query и path эндпоинта. Тело ответа возвращается как есть (текст JSON). Ответы, отличные от 2xx, отображаются как ошибки инструмента с HTTP-статусом и телом ответа.

Разработка

git clone https://github.com/subzeroid/hikerapi-mcp.git
cd hikerapi-mcp
npm install
npm run build
HIKERAPI_KEY=your-key node dist/index.js

Запуск в режиме отслеживания изменений:

HIKERAPI_KEY=your-key npm run dev

Запуск тестов (модульные + smoke-тесты stdio против локального mock-сервера, сеть/API-ключ не требуются):

npm test

Лицензия

MIT

Available Tools

44 tools
get_g2_location_by_idA
Read-only

Get an Instagram location by id: name, latitude/longitude, category and description. Use get_v1_fbsearch_places or get_v1_location_search to find the id first, and the location media tools for posts made there. Live request to Instagram, billed per call. (GET /g2/location/by/id)

Inputs: id (required).

get_g2_user_followersA
Read-only

List accounts that follow an Instagram user, one page per call. Use it to page through the follower list; use get_v1_user_search_followers to look for specific names among them and get_g2_user_following for accounts the user follows. Pass user_id; for the next page pass the cursor from the previous response as page_id. Live request to Instagram, one billed request per page. (GET /g2/user/followers)

Inputs: user_id (required), page_id.

get_g2_user_followingA
Read-only

List accounts an Instagram user follows, one page per call. Use it to page through the following list; use get_v1_user_search_following to look for specific names in it and get_g2_user_followers for the user's followers. Pass user_id; for the next page pass the cursor from the previous response as page_id. Live request to Instagram, one billed request per page. (GET /g2/user/following)

Inputs: user_id (required), page_id.

get_gql_comment_likers_chunkA
Read-only

Get users who liked one comment on an Instagram post, one page per call. Pass comment_id and media_id; paginate with end_cursor from the previous response. Use get_v2_media_likers for likers of the post itself. Live request to Instagram, billed per call. (GET /gql/comment/likers/chunk)

Inputs: media_id, comment_id, end_cursor.

get_gql_media_usertagsA
Read-only

Get the users tagged in Instagram videos; pass up to 10 media ids in media_ids. Use it for reels and videos, because the get_v2_media_info_* tools do not return user tags for video. Live request to Instagram, billed per call. (GET /gql/media/usertags)

Inputs: media_ids.

get_gql_user_aboutA
Read-only

Get the "About this account" panel for an Instagram user id: verified status, country of registration, account creation date and former usernames. Use it for account provenance checks; use get_v2_user_by_id for the regular profile. Live request to Instagram, billed per call. (GET /gql/user/about)

Inputs: id (required).

get_gql_user_mediasA
Read-only

List an Instagram user's posts, one page per call. Use it to read an account's feed; use get_v2_user_clips for reels only and get_v2_user_tag_medias for posts the user is tagged in. Pass user_id; for the next page pass the cursor from the previous response as profile_grid_items_cursor. flat=true flattens nested media objects into a single list. Live request to Instagram, billed per call. (GET /gql/user/medias)

Inputs: user_id (required), flat, profile_grid_items_cursor.

get_gql_user_repostsA
Read-only

List content an Instagram user has reposted, one page per call. Use get_gql_user_medias for the user's own posts. Pass user_id; for the next page pass the cursor from the previous response as repost_next_max_id. flat=true returns a simple items list. Live request to Instagram, billed per call. (GET /gql/user/reposts)

Inputs: user_id (required), flat, repost_next_max_id.

get_v1_fbsearch_placesA
Read-only

Search Instagram places by name (query), optionally with lat and lng. Use it to find a location id for get_g2_location_by_id and the location media tools; use get_v1_location_search when you only have coordinates. Live request to Instagram, billed per call. (GET /v1/fbsearch/places)

Inputs: query (required), lat, lng.

get_v1_hashtag_by_nameA
Read-only

Get an Instagram hashtag by exact name (no # and no special characters). Use it for the hashtag's own info; use get_v2_hashtag_medias_top or get_v2_hashtag_medias_recent for its posts and get_v1_search_hashtags when unsure of the exact tag. Live request to Instagram, billed per call. (GET /v1/hashtag/by/name)

Inputs: name (required).

get_v1_hashtag_medias_clips_chunkA
Read-only

List reels under an Instagram hashtag, one page per call. Use get_v2_hashtag_medias_top or get_v2_hashtag_medias_recent for all post types and get_v2_fbsearch_reels to search reels by free text. Pass name without #; paginate with max_id from the previous response. Live request to Instagram, billed per call. (GET /v1/hashtag/medias/clips/chunk)

Inputs: name (required), max_id.

get_v1_highlight_by_urlA
Read-only

Get one Instagram story highlight by its link. For share links that contain /s/, call get_v1_share_by_url first to resolve them. Use get_v2_highlight_by_id when you have the id. Live request to Instagram, billed per call. (GET /v1/highlight/by/url)

Inputs: url (required).

get_v1_location_medias_recent_chunkA
Read-only

List recent posts made at an Instagram location, one page per call. Pass location_pk; paginate with max_id from the previous response. Use get_v1_location_medias_top_chunk for top posts. Live request to Instagram, billed per call. (GET /v1/location/medias/recent/chunk)

Inputs: location_pk (required), max_id.

get_v1_location_medias_top_chunkA
Read-only

List top posts made at an Instagram location, one page per call. Pass location_pk; paginate with max_id from the previous response. Use get_v1_location_medias_recent_chunk for the newest posts. Live request to Instagram, billed per call. (GET /v1/location/medias/top/chunk)

Inputs: location_pk (required), max_id.

get_v1_search_hashtagsA
Read-only

Search Instagram hashtags by keyword. Use it when unsure of the exact tag; use get_v1_hashtag_by_name for one known hashtag. Live request to Instagram, billed per call. (GET /v1/search/hashtags)

Inputs: query (required).

get_v1_search_musicA
Read-only

Search Instagram music tracks by keyword (song or artist). Use get_v2_track_by_id for one known track. Live request to Instagram, billed per call. (GET /v1/search/music)

Inputs: query (required).

get_v1_share_by_urlA
Read-only

Resolve an Instagram share link (a URL that contains /s/) to the object it points to: returns its id (pk) and type. Works for stories and highlights only; then call get_v2_story_by_id or get_v2_highlight_by_id with the id. For post links use get_v2_media_info_by_url. Live request to Instagram, billed per call. (GET /v1/share/by/url)

Inputs: url (required).

get_v1_user_search_followersA
Read-only

Search within an Instagram user's followers by name or username. Use it to check whether specific accounts follow a user; use get_g2_user_followers to list all followers. Pass user_id and query; force=true skips the account privacy check. Live request to Instagram, billed per call. (GET /v1/user/search/followers)

Inputs: query (required), user_id (required), force.

get_v1_user_search_followingA
Read-only

Search within the accounts an Instagram user follows by name or username. Use it to check whether a user follows specific accounts; use get_g2_user_following to list all of them. Pass user_id and query; force=true skips the account privacy check. Live request to Instagram, billed per call. (GET /v1/user/search/following)

Inputs: query (required), user_id (required), force.

get_v2_fbsearch_accountsA
Read-only

Search Instagram accounts by keyword. Use it to find a profile when you do not know the exact handle; use get_v2_user_by_username for an exact handle. Paginate with page_token from the previous response. Live request to Instagram, billed per call. (GET /v2/fbsearch/accounts)

Inputs: query (required), safe_int, page_token.

get_v2_fbsearch_reelsA
Read-only

Search Instagram reels by keyword. Use it to find short videos about a topic; use get_v1_hashtag_medias_clips_chunk for reels under one specific hashtag. Paginate with reels_max_id and rank_token from the previous response. Live request to Instagram, billed per call. (GET /v2/fbsearch/reels)

Inputs: query (required), safe_int, rank_token, reels_max_id.

get_v2_fbsearch_topsearchA
Read-only

Search Instagram for top content by keyword. Use it for a broad first look; use get_v2_fbsearch_accounts to search only accounts, get_v2_fbsearch_reels only reels and get_v1_search_hashtags only hashtags. Paginate with next_max_id from the previous response. Live request to Instagram, billed per call. (GET /v2/fbsearch/topsearch)

Inputs: query (required), safe_int, next_max_id.

get_v2_hashtag_medias_recentA
Read-only

List recent posts under an Instagram hashtag, one page per call. Use get_v2_hashtag_medias_top for top posts and get_v1_hashtag_medias_clips_chunk for reels only. Pass name without #; for the next page pass next_page_id from the previous response as page_id. Live request to Instagram, billed per call. (GET /v2/hashtag/medias/recent)

Inputs: name (required), page_id, safe_int.

get_v2_hashtag_medias_topA
Read-only

List top posts under an Instagram hashtag, one page per call. Use get_v2_hashtag_medias_recent for the newest posts and get_v1_hashtag_medias_clips_chunk for reels only. Pass name without #; for the next page pass next_page_id from the previous response as page_id. Live request to Instagram, billed per call. (GET /v2/hashtag/medias/top)

Inputs: name (required), page_id, safe_int.

get_v2_highlight_by_idA
Read-only

Get one Instagram story highlight by id. Use get_v2_user_highlights to list a user's highlights and get_v1_highlight_by_url when you have a link. Live request to Instagram, billed per call. (GET /v2/highlight/by/id)

Inputs: id (required), safe_int.

get_v2_media_commentsA
Read-only

Get comments on an Instagram post, about 15 per call. Pass the media id; for the next page pass the page id from the previous response as page_id. Use get_v2_media_comments_replies for replies under one comment and get_v2_media_likers for users who liked the post. Live request to Instagram, one billed request per page. (GET /v2/media/comments)

Inputs: id (required), page_id, safe_int, can_support_threading.

get_v2_media_comments_repliesA
Read-only

Get replies under one comment of an Instagram post. Use it to read a thread; use get_v2_media_comments for the top-level comments. Pass media_id and comment_id (both from the comments tool); paginate with min_id from the previous response. Live request to Instagram, billed per call. (GET /v2/media/comments/replies)

Inputs: media_id (required), comment_id (required), min_id, safe_int.

get_v2_media_info_by_codeA
Read-only

Get an Instagram post or reel by its shortcode (the part after /p/ or /reel/ in the link). Use get_v2_media_info_by_url when you have a full link and get_v2_media_info_by_id for a numeric media id. Returns the media object, or 404 for deleted or unavailable posts; promoted (ad) posts may also return 404. User tags are not included for videos, use get_gql_media_usertags for those. Live request to Instagram, billed per call. (GET /v2/media/info/by/code)

Inputs: code (required), safe_int.

get_v2_media_info_by_idA
Read-only

Get an Instagram post or reel by numeric media id. Use get_v2_media_info_by_code for a shortcode and get_v2_media_info_by_url for a full link. Returns the media object, or 404 for deleted or unavailable posts; promoted (ad) posts may also return 404. User tags are not included for videos, use get_gql_media_usertags for those. Live request to Instagram, billed per call. (GET /v2/media/info/by/id)

Inputs: id (required), safe_int.

get_v2_media_info_by_urlA
Read-only

Get an Instagram post or reel by its link (instagram.com/p/... or /reel/...). Use get_v2_media_info_by_code for a bare shortcode. Returns the media object, 404 for deleted or unavailable posts and 400 for links that are not posts: use get_v2_story_by_url for story links and get_v1_share_by_url for /s/ share links. Promoted (ad) posts may also return 404. Live request to Instagram, billed per call. (GET /v2/media/info/by/url)

Inputs: url (required), safe_int.

get_v2_media_likersA
Read-only

Get users who liked an Instagram post, by media id. Use get_gql_comment_likers_chunk for likers of a single comment and get_v2_media_comments for commenters. Live request to Instagram, billed per call. (GET /v2/media/likers)

Inputs: id (required), safe_int.

get_v2_story_by_idA
Read-only

Get one Instagram story by its id. Use get_v2_story_by_url when you have a story link and get_v2_user_stories to list a user's active stories. Live request to Instagram, billed per call. (GET /v2/story/by/id)

Inputs: id (required), safe_int.

get_v2_story_by_urlA
Read-only

Get one Instagram story by its link. For share links that contain /s/, call get_v1_share_by_url first to resolve them. Use get_v2_story_by_id when you have the id. Live request to Instagram, billed per call. (GET /v2/story/by/url)

Inputs: url (required), safe_int.

get_v2_track_by_idA
Read-only

Get an Instagram music track by track_id. Use get_v1_search_music to find tracks by keyword. For the next page pass next_page_id from the previous response as page_id. Live request to Instagram, billed per call. (GET /v2/track/by/id)

Inputs: track_id (required), page_id, safe_int.

get_v2_user_by_idA
Read-only

Get an Instagram profile by numeric user id. Use it when you already have the id from another tool; use get_v2_user_by_username when you only have a handle. Returns the same user object. Live request to Instagram, billed per call. (GET /v2/user/by/id)

Inputs: id (required), safe_int.

get_v2_user_by_usernameA
Read-only

Get an Instagram profile by username (without @). Use it when you have a handle; use get_v2_user_by_id when you already know the numeric user id (faster), and get_gql_user_about for the "About this account" panel. Returns the user object; pass its pk as the user id to the other user tools. Live request to Instagram, one billed request per call. (GET /v2/user/by/username)

Inputs: username (required), safe_int.

get_v2_user_clipsA
Read-only

List an Instagram user's reels (short videos), one page per call. Use it for reels only; use get_gql_user_medias for all posts. Pass user_id; for the next page pass next_page_id from the previous response as page_id. Live request to Instagram, billed per call. (GET /v2/user/clips)

Inputs: page_id, user_id, safe_int.

get_v2_user_highlightsA
Read-only

List an Instagram user's story highlights (saved story collections) by user id, one page per call. Use get_v2_highlight_by_id to open one highlight and get_v2_user_highlights_by_username when you only have a handle. For the next page pass next_page_id from the previous response as page_id (amount is ignored). Live request to Instagram, billed as 2 requests per call. (GET /v2/user/highlights)

Inputs: user_id (required), force, amount, page_id, +1 more.

get_v2_user_highlights_by_usernameA
Read-only

List an Instagram user's story highlights by username, one page per call. Use it only when you have a handle and not the user id: it is slower than get_v2_user_highlights and billed as 3 requests per call instead of 2. For the next page pass next_page_id from the previous response as page_id. Live request to Instagram. (GET /v2/user/highlights/by/username)

Inputs: username (required), force, amount, page_id, +1 more.

get_v2_user_storiesA
Read-only

Get an Instagram user's active stories by user id. Use it when you have the id; use get_v2_user_stories_by_username when you only have a handle and get_v2_user_highlights for saved highlight collections. force=true skips the account privacy check. Live request to Instagram, billed as 2 requests per call. (GET /v2/user/stories)

Inputs: user_id (required), force, safe_int.

get_v2_user_stories_by_usernameA
Read-only

Get an Instagram user's active stories by username. Use it only when you have a handle and not the user id: it is slower than get_v2_user_stories and billed as 3 requests per call instead of 2. Live request to Instagram. (GET /v2/user/stories/by/username)

Inputs: username (required), force, safe_int.

get_v2_user_suggested_profilesA
Read-only

Get the accounts Instagram suggests as related to a given user. Use it to find similar accounts; use get_v2_fbsearch_accounts to search accounts by keyword instead. Pass user_id; expand_suggestion=true returns more detail per account. Live request to Instagram, billed per call. (GET /v2/user/suggested/profiles)

Inputs: user_id (required), safe_int, expand_suggestion.

get_v2_user_tag_mediasA
Read-only

List posts in which an Instagram user is tagged, one page per call. Use it to see who features an account; use get_gql_user_medias for the user's own posts. Pass user_id; for the next page pass next_page_id from the previous response as page_id. Live request to Instagram, billed per call. (GET /v2/user/tag/medias)

Inputs: page_id, user_id, safe_int.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 44 tools

    Disambiguation4/5

    The tools cover many distinct Instagram resources and actions, and descriptions explicitly cross-reference alternatives such as by id vs username vs URL vs shortcode, or top vs recent vs clips. While no two tools are truly interchangeable, the sheer number of near-variants increases cognitive load and misselection risk.

    Naming Consistency4/5

    All tools use a get_ + lowercase snake_case convention, making the pattern predictable. Minor inconsistency comes from mixed API-version prefixes (v1, v2, gql, g2) and compound tokens like fbsearch, usertags, and clips_chunk, but the naming remains readable and largely consistent.

    Tool Count2/5

    44 tools far exceeds the typical 3-15 range and includes many access-method variants that could be consolidated into fewer flexible tools. While each maps to a real endpoint, the set is heavy and likely to overwhelm tool selection.

    Completeness4/5

    The surface covers users, media, comments, likes, stories, highlights, search, hashtags, locations, music, followers/following, suggestions, and account provenance, giving broad read-only Instagram coverage. Gaps exist for less common data such as live videos, saved media, or media by music track, but core workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for LamaTok TikTok data API — auto-generates 20+ tools from the live OpenAPI spec (users, videos, hashtags, music, comments). Local stdio via npx -y lamatok-mcp, requires only LAMATOK_KEY.
      23
      44 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for DataLikers — 51 tools for Instagram & TikTok data: Instagram user search by demographics (gender/age/race/country/city), profiles, engagement, posts, comments, hashtags, locations, stories, business accounts; TikTok users, videos, comments, hashtags, playlists. Local stdio via npx -y datalikers-mcp, requires only DATALIKERS_API_KEY.
      53 npm
      9
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      16 Instagram creator tools as an MCP server — Reels/Story/carousel downloaders, engagement audit, hashtag search, Reels hook generator, best-time-to-post and content calendar. Wraps instapdown.com public API — no auth required.
      16
      51 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for downloading Instagram content (videos, reels, audio, carousels) using yt-dlp, with tools for downloading media and fetching metadata. Supports stdio and HTTP transports.
      MIT