Pulpie MCP
Related Servers
Alternatives to Pulpie MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that converts web pages to clean Markdown for LLMs via two paid tools: surface_markdown_parser and stealth_markdown_parser.126 npm-
- AlicenseAqualityDmaintenanceMCP server that allows AI agents to fetch and process llms.txt documentation from various sources. Fetch documentation from any HTTPS URL and automatically convert HTML content to readable markdown.24 npm2MIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server for web content extraction that converts HTML pages into clean, LLM-optimized Markdown using Mozilla's Readability. It supports batch processing, intelligent multi-page crawling, and configurable caching while respecting robots.txt standards.32 npm-
- AlicenseNot gradedqualityAmaintenanceMCP server that fetches and converts website pages into clean markdown for agents, with sitemap-based discovery, disk caching, and polite crawling (robots.txt, rate limiting).6 npm2MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to search the web and extract clean Markdown content, with support for JavaScript rendering, structured data extraction, and screenshots.2-
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that extracts clean, structured Markdown content from web page URLs using the WebforAI library. It simplifies feeding web content into AI models by removing HTML noise and intelligently processing tables and links.-
TDQS
Scored across 5 tools
fetch_markdown and save_markdown are the only pair with overlapping purposes, but the save/no-save distinction is clearly stated. list_library, search_library, and crawl_docs each target a distinct operation with no real ambiguity.
All five tools follow a clean verb_noun snake_case pattern (fetch_markdown, save_markdown, crawl_docs, list_library, search_library). The convention is applied uniformly and reads predictably.
Five tools is a tight, well-scoped set for a fetch/save/search docs server. Each tool earns its place with no redundancy.
The lifecycle covers fetch, persist, bulk-crawl, browse, and search. Minor gaps exist: no tool to delete or remove a saved doc, and no direct read of a specific saved file, but these are workaroundable.