@gluedly/mcp-server
OfficialRelated Servers
Alternatives to @gluedly/mcp-server
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEU-native web scraping for AI agents & developers. scrape web pages into markdown, screenshots, metadata, and links, map sites, run asynchronous scrape jobs, and check usage, with EU-hosted, GDPR-aligned processing.7179 npm1Apache 2.0
FlyCrawl MCP Serverofficial
AlicenseAqualityCmaintenanceEnables Claude Desktop, Cursor AI, Windsurf, and autonomous LLM agents to scrape, crawl, map, search, and extract validated JSON from live web pages with dynamic rendering, anti-bot bypass, and Markdown conversion.521 npmMIT- AlicenseBqualityBmaintenanceWeb scraping for AI agents: scrape, map, crawl and batch public pages into Markdown, tables and JSON, with an Evidence Record on every page. Blocked, empty and wrong pages come back as such, with the reason.397AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to read public webpages as Markdown or HTML, discover links, extract structured JSON, and perform bounded crawls.AGPL 3.0
- AlicenseAqualityBmaintenanceLets AI agents like Claude capture website screenshots, check cache status, and monitor usage.113MIT
- FlicenseNot gradedqualityDmaintenanceEnables scraping single pages or crawling entire websites, converting content to markdown and optionally extracting structured data with Claude.-
TDQS
Scored across 3 tools
Each tool serves a distinct phase of the scraping workflow: listing pages, triggering a scrape, and fetching snapshot data. There is no functional overlap or ambiguity between the tools.
All tool names follow the same pattern: the 'gluedly_' prefix followed by a verb_noun (list_pages, trigger_scrape, get_snapshot). This makes the tool set highly predictable and easy to navigate.
Three tools is minimal but well-scoped for the server's purpose of interacting with an existing Gluedly scraping workflow. Each tool fills a necessary role, and the count is within the ideal range.
The server covers the essential end-to-end flow: list pages, trigger a scrape, and collect the extracted data. It lacks CRUD/manage capabilities for pages, but this is likely outside the MCP server's intended scope and easily workable.