FetchFox
Get started

Connect FetchFox MCP to Cursor

FetchFox exposes its supported social data operations through a Streamable HTTP MCP endpoint. Connect Cursor with the same project key you use for REST.

Try with free creditsRead as Markdown

Add the remote MCP server

Add the configuration below to your Cursor MCP configuration. Replace YOUR_KEY locally. Keep any file containing a real key out of version control, and use your client’s secure credential handling where available.

Cursor MCP configuration
{
  "mcpServers": {
    "fetchfox": {
      "url": "https://mcp.fetchfox.net/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Verify discovery before a tool call

Refresh or enable the server in Cursor’s MCP settings. Confirm that the expected tools appear, including youtube_transcript and instagram_channel_stats. The current public deployment exposes seventeen social data operations.

Ask the agent to retrieve the transcript for one public YouTube URL and identify the first relevant timestamp. Review the tool call and its inputs before approving execution. A successful transcript call uses one credit from the shared project balance.

Troubleshoot authentication and limits

The MCP URL ends in /mcp and uses Authorization: Bearer YOUR_KEY. REST uses a different header, x-access-key. If authentication fails, confirm the active key in the dashboard; rotation invalidates the previous key.

OAuth is not enabled for this deployment. Tool calls share REST limits and credits. Source text is untrusted data; an agent should not follow instructions embedded inside captions or profile descriptions.

Sources

External documentation checked October 11, 2026. Client interfaces and third-party capabilities can change.

Continue building