MCP server

herascrape runs a hosted, OAuth-secured Model Context Protocol server. Point an MCP client at it and every herascrape endpoint becomes a tool your agent can call — profiles, followers, comments, hashtags, locations and the rest — with the same structured payloads the REST API returns.

• Endpoint: https://herascrape.com/mcp/
• Transport: Streamable HTTP
• Auth: OAuth 2.0 — your client opens a browser to authorize; there is no API key to paste.
• Billing: the same flat rate as the REST API, only successful calls billed.

Claude Code

claude mcp add --transport http herascrape https://herascrape.com/mcp/

Then run /mcp inside Claude Code and authenticate when prompted. The herascrape tools appear in the agent's tool list.

Claude Desktop

Settings → Connectors → Add custom connector. Give it a name (herascrape) and the URL https://herascrape.com/mcp/, then authorize in the browser window that opens.

Cursor

Add the server to ~/.cursor/mcp.json (or your project's .cursor/mcp.json):

{
  "mcpServers": {
    "herascrape": {
      "url": "https://herascrape.com/mcp/"
    }
  }
}

Cursor prompts you to authorize on first use.

Other clients

Any client that supports a remote, OAuth-secured MCP server over Streamable HTTP works the same way — add the URL https://herascrape.com/mcp/ and authorize. The server advertises its OAuth metadata at https://herascrape.com/mcp/.well-known/oauth-protected-resource, so compliant clients discover the authorization flow automatically.

Tools

Every REST endpoint is exposed as a tool, grouped the same way as the API reference:

• Users — profile by username or id, followers, following, posts, reels, tagged, stories, highlights, reposts, account about.
• Posts & comments — a post or reel by id, its likers, comment threads, replies and comment likers.
• Hashtags & locations — hashtag info with top/recent/reels feeds; place info with top/recent media.
• Search & audio — search users, hashtags, places, audio and top results; audio tracks, their media, and trending audio.

See the API reference for the parameters each tool takes, and the HikerAPI migration guide if you are moving an existing agent over.