pulse-fetch MCP Server

What this does

pulse-fetch exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

FIRECRAWL_API_KEY
BRIGHTDATA_API_KEY
STRATEGY_CONFIG_PATH
OPTIMIZE_FOR
MCP_RESOURCE_STORAGE
MCP_RESOURCE_FILESYSTEM_ROOT
SKIP_HEALTH_CHECKS
LLM_PROVIDER
LLM_API_KEY
LLM_API_BASE_URL
LLM_MODEL

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install pulse-fetch?

Run the Claude Code command in the install section to add pulse-fetch to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with pulse-fetch?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to pulse-fetch as well.

Does pulse-fetch need an API key?

Yes. Before it can run, set these environment variables: FIRECRAWL_API_KEY, BRIGHTDATA_API_KEY, STRATEGY_CONFIG_PATH, OPTIMIZE_FOR, MCP_RESOURCE_STORAGE, MCP_RESOURCE_FILESYSTEM_ROOT, SKIP_HEALTH_CHECKS, LLM_PROVIDER, LLM_API_KEY, LLM_API_BASE_URL, LLM_MODEL. They go in the env block of your MCP config.