Momor's Docs Are Live, and Your AI Tools Can Read Them Too
The Momor Team · Oct 23, 2026 · 3 min read
Products are only as usable as their documentation. Momor now has real docs for Gateway and Workflows, written from the code, and published in a form your coding assistant can read as easily as you can.
Highlights
- Docs for Momor Gateway and Momor Workflows at momor.ai/docs
- Every endpoint on its own reference page, with examples in curl, Python, TypeScript and C#
- The same docs served over MCP, so AI tools can search and read them
- Updates now live in the Blog, with one RSS feed for everything
Docs at momor.ai/docs
The Gateway docs start with a quickstart and cover authentication, credits, choosing a model, streaming, tools, structured output, files, failover, bringing your own keys, usage and rate limits, with a reference page for every endpoint. The Workflows docs cover the core ideas, steps, waits, runs and recovery, the knowledge graph, tool servers, hooks, versions, limits and the YAML reference, with worked examples such as a refund approval and invoice matching.
Docs your AI tools can read
Each product's docs are also an MCP server, at mcp.momor.ai/docs/gateway and mcp.momor.ai/docs/workflows. Connect one to your AI tool and it gets two tools: search_docs, which finds the pages that best match a question, and read_page, which returns a page as Markdown. No sign-in is needed. On every docs page, the menu beside Copy page has "Connect docs to your AI tool", which copies the address.
Updates found a home
Updates moved into the Blog as their own tab, at /blog/updates/. Old Updates addresses still lead to their posts. The Blog's feed, /blog/rss.xml, carries every post, Updates included, so one subscription catches everything.
Why This Matters
More and more code is written with an assistant in the loop. If that assistant can search Momor's docs directly, it writes a correct Gateway call or workflow on the first try instead of guessing at field names.
What this means for you: read the docs at momor.ai/docs, point your coding assistant at the docs MCP server, and follow every update through a single feed.