What happened?
Not a bug. This is docs feedback and a contribution proposal.
The docs at py.sdk.modelcontextprotocol.io are English-only. I couldn't find an Arabic version, and I'm not sure what the repo's i18n/ folder is for, since I couldn't tell whether it holds translations or what format they use.
I'm a native Arabic speaker and full-stack developer (Python/FastAPI, building MCP-based tooling for clients in the Middle East). Arabic-speaking developers are a real audience for MCP servers and clients, and an Arabic version of the docs would lower the barrier for them.
Before writing anything, I want to check whether this is wanted and how you'd like it done.
What did you expect?
A clear answer on:
- Are community translations of the docs accepted? If yes, is
i18n/ the right place, and what format/workflow should I follow (mkdocs i18n plugin, per-language directories, etc.)?
- Which pages to start with? My suggestion is README + Get started, in one small PR, then expand page by page.
- How translation drift should be handled as v2 evolves. I'm willing to maintain Arabic and keep it in sync with changes to the English pages.
- Any glossary or conventions for technical terms (tool, resource, prompt, transport, etc.) so terminology stays consistent.
Per CONTRIBUTING.md, I will not open a PR until a maintainer confirms this is welcome. If AI assistance is used for first drafts, I'll disclose it in the PR and review every line myself.
Code to reproduce
N/A (docs feedback). Page: https://py.sdk.modelcontextprotocol.io/
SDK version
N/A (docs). Observed on main, October 2026.
Area
Documentation
What happened?
Not a bug. This is docs feedback and a contribution proposal.
The docs at py.sdk.modelcontextprotocol.io are English-only. I couldn't find an Arabic version, and I'm not sure what the repo's
i18n/folder is for, since I couldn't tell whether it holds translations or what format they use.I'm a native Arabic speaker and full-stack developer (Python/FastAPI, building MCP-based tooling for clients in the Middle East). Arabic-speaking developers are a real audience for MCP servers and clients, and an Arabic version of the docs would lower the barrier for them.
Before writing anything, I want to check whether this is wanted and how you'd like it done.
What did you expect?
A clear answer on:
i18n/the right place, and what format/workflow should I follow (mkdocs i18n plugin, per-language directories, etc.)?Per CONTRIBUTING.md, I will not open a PR until a maintainer confirms this is welcome. If AI assistance is used for first drafts, I'll disclose it in the PR and review every line myself.
Code to reproduce
SDK version
N/A (docs). Observed on main, October 2026.
Area
Documentation