mdisbetter MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MDISBETTER_API_KEY | Yes | Your mdisbetter.com API key, starting with mdb_sk_. Required. | |
| MDISBETTER_BASE_URL | No | Base URL of the mdisbetter.com service. Defaults to https://mdisbetter.com. Point it at a preview deployment to test against one. | https://mdisbetter.com |
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 |
|---|---|
| convert_fileA | Convert one local file to another format and write the result next to it. Covers 3649 proven conversions across 162 input formats (images, documents, ebooks, and office files to PDF). Call list_conversions first if you are unsure a pair is supported. One file per call: there is no batch mode. |
| list_conversionsA | Ask what this converter can do. With an extension, returns the output formats proven for it. With no argument, returns every input extension accepted. |
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
convert_file and list_conversions have clearly distinct purposes: one performs an action and the other provides capability information. There is no overlap or ambiguity between them.
Both tools follow the same verb_noun snake_case pattern: convert_file and list_conversions. The naming is consistent and predictable.
Two tools is minimal, but it fits the server's narrow purpose: querying supported conversions and performing a conversion. It is slightly under the typical well-scoped range but not overly thin.
The server fully covers its domain: list_conversions tells agents what is possible, and convert_file performs the conversion. There are no obvious dead ends for the stated single-file conversion workflow.