MCP server
These docs are an MCP server. Connect it once and your coding assistant reads the documentation itself — searching it, opening pages, pulling an endpoint's exact request and response schema — instead of you pasting pages into a chat window.
Connect it
One URL, https://docs.munsit.com/api/mcp. No key, no auth, nothing to install — the docs are public and so is the server.
https://docs.munsit.com/api/mcp as a custom connector under Settings → Connectors. Any client that takes a remote MCP URL will take this one.
What your assistant gets
Five tools. The first two are the ones it will reach for most: find the right page, then read it.
| Tool | Arguments | What comes back |
|---|---|---|
| search_docs | query, limit | The pages matching a question, ranked, each with the excerpt that matched. Arabic queries work as well as English. |
| get_page | path | One page as Markdown, every code sample included. Takes /errors, errors, /errors.md or a full URL. |
| list_pages | — | The whole documentation index, grouped as the sidebar groups it, one line per page. |
| list_endpoints | query | Every REST operation from the OpenAPI spec: method, path, summary. Filterable. |
| get_endpoint | path, method | One operation's full OpenAPI definition — parameters, request body, responses — with every $ref inlined, so it reads as one self-contained document. |
Ask for a working integration and it goes and gets what it needs:
Without MCP
Everything the server exposes is a plain URL too, for a tool that only fetches. Nothing here needs a key either.
Working with an AI assistant? Every page is available as Markdown: add .md to the URL, or send an Accept: text/markdown header. For the whole documentation in one request, point it at llms-full.txt; the page index is llms.txt. Or use Copy Page, top right.
