web2md-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEB2MD_API_KEY | Yes | Your API key from web2md.org |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_urlA | Convert a webpage URL to clean Markdown. Returns the Markdown content and metadata (title, word count, reading time). |
| semantic_searchA | Search your saved conversions using natural language. Works across languages. |
| get_conversionA | Retrieve the full Markdown content of a previously saved conversion by its ID. |
| bridge_convert_urlA | Convert a URL using your Chrome extension — required for Reddit, JS-rendered sites, or login-protected pages. The Web2MD extension must be installed and running in Chrome. Auto-discovers your extension ID via your API key. |
| agent_convertA | Convert a URL using the Chrome extension via native messaging. Best for Reddit, login-protected pages, and JS-rendered sites. Requires: Chrome running + Web2MD extension + native host installed. |
| agent_batch_convertA | Batch convert multiple URLs using the Chrome extension via native messaging. Ideal for converting many Reddit threads or JS-rendered pages. URLs are processed sequentially. Requires: Chrome running + Web2MD extension + native host installed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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 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.
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.
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.