Been doing a lot of competitive research for clients lately — checking hashtag volumes, tracking top posts in a niche, that kind of thing. Kept switching between Claude Code and browser tabs to cross-reference stuff manually. Got annoying fast.
Found hikerapi-mcp, a Model Context Protocol server that exposes 100+ Instagram endpoints as tools directly inside Claude Code. Figured I'd try it.
Setup was straightforward. The one thing I did differently was keeping the API key out of config files entirely — passed it as an environment variable instead. Smaller attack surface if I accidentally commit something.
Also filtered down the tool groups with HIKERAPI_TAGS because 100+ tools showing up in context is chaos. I only need hashtag search and competitor profile data, so I scoped it to just those.
"env": {
"HIKERAPI_KEY": "${HIKERAPI_KEY}",
"HIKERAPI_TAGS": "User Profile,Post Details,Search,Hashtags,Stories"
}
One thing that tripped me up for a solid 20 minutes: HikerAPI runs on a prepaid model (credits in rubles). If your balance is zero, you get HTTP 402, not 401. I kept thinking my key was invalid and regenerated it twice before I figured out I just needed to top up.
Once that was sorted, it actually works well. Now I can ask things like "what are the top 10 posts for #socialmediamarketing this week" or pull a competitor's recent content directly in the same session where I'm building the campaign strategy. Cuts out a lot of context switching.
Repo if you want to check it out: github.com/subzeroid/hikerapi-mcp
Wrote up the full setup with config details here if useful: https://dev.to/simrp360/querying-instagram-from-claude-code-wiring-up-hikerapis-mcp-server-57jf
Anyone else using MCP servers for social data research? Curious what other setups people are running.
Top comments (0)