Skip to main content
Glama
io-oi-ai

web2md-mcp

by io-oi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to web2md-mcp

No user-submitted related servers found.

    Related Servers

    • octen-mcp by Octen-Team

      octen-mcpofficial

      Octen-Team
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Octen Extract that turns any URL into clean, LLM-ready markdown, with highlights and classification. Works with Claude, Cursor, VS Code, and other MCP clients.
      6
      108 npm
      16
      MIT

    • NodeProxy

      pgalyen1987
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that converts web pages to clean Markdown for LLMs via two paid tools: surface_markdown_parser and stealth_markdown_parser.
      559 npm
      -

    • webfetch

      ChesterNotChest
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that fetches any http/https webpage, extracts main content, and converts it to Markdown, serving as a drop-in replacement for the built-in WebFetch tool.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation2/5

    The three URL conversion tools (convert_url, bridge_convert_url, agent_convert) create significant overlap, especially for Reddit/JS/login-protected pages, where bridge_convert_url and agent_convert seem to serve the same purpose. The descriptions attempt to distinguish them by method, but an agent will struggle to know which to choose. semantic_search and get_conversion are distinct, but the converter cluster muddies the set.

    Naming Consistency2/5

    Naming conventions are mixed: convert_url and get_conversion follow verb_noun, while semantic_search is a compound noun, and bridge_convert_url, agent_convert, agent_batch_convert use method prefixes (bridge_, agent_) rather than consistent action-first names. This inconsistency makes the tool surface harder to predict.

    Tool Count5/5

    With 6 tools, the count is well within the ideal range for a focused web-to-markdown server. Each tool has a clear role in the conversion and retrieval workflow, including variations for extension-based conversion and batch processing. No bloat or trivial tools.

    Completeness3/5

    The core lifecycle is covered: convert, retrieve by ID, and search. However, there is no list-all-conversions tool and no delete/update operation, leaving a notable gap in managing saved conversions. The presence of three overlapping conversion methods partly compensates for missing features but also adds confusion.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources