urltomarkdown-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_url_to_markdownA | Fetch a URL and convert its web page content to clean Markdown |
| convert_html_to_markdownB | Convert raw HTML to clean Markdown |
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 2 tools
Both tools convert content to Markdown but accept fundamentally different inputs: raw HTML vs. a URL. Their purposes are clearly distinct, with no overlap.
Both tool names follow the consistent 'convert_<source>_to_markdown' pattern, using snake_case and clear verb-noun structure.
With only two tools, the server is minimal but well-scoped for its domain of converting to Markdown. The count matches the simple purpose.
The server covers the two primary input types: raw HTML and URL. It is lacking file-based input, but for a specialized MCP server, this coverage is reasonable.