Link MCP
Related Servers
Alternatives to Link MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and IDE workflows to fetch and crawl webpages locally, extracting readable content and converting it to token-efficient Markdown with preserved links.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to crawl websites, extract and store web content with semantic search capabilities using vector embeddings, and retrieve information through natural language queries with tag-based filtering and intelligent content cleaning.-
- FlicenseNot gradedqualityDmaintenanceEnables crawling and extracting clean content from documentation websites with optional LLM-powered analysis for intelligent summaries, code example extraction, and content classification.-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents and coding assistants with advanced web crawling and RAG capabilities, allowing them to scrape websites and leverage that knowledge through various retrieval strategies.2MIT
- AlicenseNot gradedqualityDmaintenanceProvides web crawling and RAG capabilities for AI agents, enabling scraping of websites, storing content in a vector database (Supabase), and performing semantic search over crawled data.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and LLM pipelines to fetch webpages or crawl sites, extract main content, and convert it to clean, token-efficient Markdown with preserved links. It supports configurable crawling depth, caching, robots.txt compliance, and optional chunking for downstream processing.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap. fetch_link_documentation handles web documentation extraction, get_cursor_memories retrieves saved memories, and save_cursor_memory stores new memories. The domains (web analysis vs. memory management) and actions (fetch, get, save) are completely separate, eliminating any risk of misselection.
The tools follow a consistent verb_noun pattern with snake_case throughout (fetch_link_documentation, get_cursor_memories, save_cursor_memory). The minor deviation is that two tools use plural 'memories' while one uses singular 'memory', but this doesn't affect readability or predictability.
With only 3 tools, the server feels thin for a 'Link MCP' server that implies broader link/documentation capabilities. While the tools cover distinct functions, the count is borderline low for a server that might be expected to handle more link-related operations beyond just documentation fetching and memory management.
There are significant gaps in the tool surface for a link/documentation server. While documentation fetching and memory tools exist, there's no basic link validation, metadata extraction, content summarization without saving, or other common link processing operations. The memory tools are well-covered, but the link/documentation domain is severely incomplete.