Using mdcraft with agents via MCP#

mdcraft does not have a public MCP server yet.

Current status#

• The current integration surface is the Files to Markdown API beta.
• MCP support is not public yet.
• The browser studio remains the easiest way to evaluate output quality.

What to use today#

If you want to use mdcraft in software or automation today:

• request API beta access
• convert files through the API
• use conversionId to fetch results and track usage

Expected MCP surface#

When MCP support is published, the tool surface is expected to stay narrow:

• convert_file_to_markdown
• get_conversion_result
• list_supported_formats
• get_conversion_warnings

Security boundaries#

The intended boundaries are:

• no arbitrary filesystem access
• no repo-local execution
• no open-ended browsing behavior
• strict file size and format limits
• explicit retention and privacy disclosure

Why it follows the API#

The API comes first so auth, limits, warnings, and result tracking stay consistent across every integration surface.

Summary#

Today, use the studio or the API beta. Treat MCP support as upcoming, not current.