Pulse-fetch MCP Server

Pulse-fetch is an MCP integration. MCP server for fetching web resources with content extraction and anti-bot bypass.

Packages and local setup

The published npm package is @pulsemcp/pulse-fetch, version 0.3.3. Its declared MCP transport is stdio.

The package declares FIRECRAWL_API_KEY: API key for Firecrawl service to bypass anti-bot measures.; BRIGHTDATA_API_KEY: Bearer token for BrightData Web Unlocker service.; STRATEGY_CONFIG_PATH: Path to markdown file containing scraping strategy configuration.; OPTIMIZE_FOR: Optimization strategy for scraping: cost or speed.; MCP_RESOURCE_STORAGE: Storage backend for saved resources: memory or filesystem.; MCP_RESOURCE_FILESYSTEM_ROOT: Directory for filesystem storage of resources.; SKIP_HEALTH_CHECKS: Skip API authentication health checks at startup.; LLM_PROVIDER: LLM provider for extraction: anthropic, openai, or openai-compatible.; LLM_API_KEY: API key for the chosen LLM provider.; LLM_API_BASE_URL: Base URL for OpenAI-compatible LLM providers.; LLM_MODEL: Specific LLM model to use for extraction..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.3.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.