AI Glot websiteOpen AI Glot
File formatsMarkdown
File formats

Translate Markdown files

Translate .md, .markdown and .mdx files up to 4 MB. Code, link targets and structure stay intact, and front matter titles are translated. Example instructions included.

Markdown files (.md, .markdown and .mdx) are accepted up to 4 MB. AI Glot reads headings, paragraphs, list items and table cells as text and everything else as structure, so the file is ready to commit.

What is translated, and what is left alone

TranslatedLeft as it was
Headings, paragraphs, list items, quotes and table cellsFenced and indented code, inline code
Link text and emphasis, moved with the right wordsLink targets and URLs
Front matter title and descriptionOther front matter fields such as slugs, dates and tags
The words around inline codeHTML blocks, MDX imports, component tags and expressions

Line endings and a byte-order mark are kept too.

What you can ask

Docs page

The common case: translate prose, leave code and links alone.

Translate into French. Leave code blocks, inline code and URLs alone, and keep the product name Acme in English.

README

Keeps the badges and installation commands intact.

Translate this README into German. Leave badges, shell commands and file names exactly as they are.

Blog post with front matter

Translates title and description and leaves the slug.

Translate into Spanish, including the front matter title and description. Do not change the slug, date or tags.

MDX component props

Keeps components working while the surrounding text is translated.

Translate the prose into Italian. Leave imports, component tags and their props unchanged.

Informal tone

Chooses the register for the target language.

Translate into Portuguese. Use an informal, friendly tone and address the reader as “você”.

Good to know

  • One target language per upload. A file holds one language. If you ask for two, the plan translates one and says so. Run the file once per language: your glossary carries over.
  • A whole docs folder. Put the files in a ZIP to translate them in one job and keep the folder layout.
  • Ceiling. 4 MB. Output filter: not available, the whole file comes back.
  • Component text in MDX. Text passed as component props is not prose. If a prop holds words people read, say so in your instruction.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search AI Glot Docs documentation and read it in full, instead of answering from memory.

https://ai-glot.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://ai-glot.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.