tokenmarkdown-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOKENMARKDOWN_API_KEY | Yes | Your TokenMarkdown API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_markdownA | Sub-150ms clean web-to-markdown extraction. Strips 95% of HTML bloat, cookie banners, tracking scripts, and SVGs to preserve LLM context windows. |
| check_quotaA | Check remaining TokenMarkdown API credits and usage status. |
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
The two tools have completely distinct purposes: one performs the core extraction, the other monitors usage. There is no possible confusion between them.
Both tool names follow the same verb_noun pattern (extract_markdown, check_quota), creating a predictable and clean naming convention.
With only two tools, the count is slightly under the typical 3-15 range, but it fits the narrow scope of a single-purpose extraction API with quota checking. No unnecessary tools are present.
The tool surface fully covers the service's obvious domain: extracting web content to markdown and checking API quota. There are no missing operations for this focused utility.