> ## Documentation Index
> Fetch the complete documentation index at: https://hyperlocalise.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer integrations

> Choose the CLI, public API, or hosted MCP server for your Platform workflow.

Use the CLI, public API, or hosted MCP server to connect your own tools to Platform. These guides are for customers integrating a workspace into their product and delivery process.

| Interface  | Use it for                                                                    | Start here                       |
| ---------- | ----------------------------------------------------------------------------- | -------------------------------- |
| CLI        | Push repository sources and pull target files using locale path configuration | [Connect the CLI](/platform/cli) |
| Public API | Build file upload, translation-job, status, and download flows                | [Public API](/platform/api)      |
| Hosted MCP | Let an authorized AI agent work with Platform tools                           | [MCP server](/platform/mcp)      |

Organization keys suit shared CI workflows. Personal tokens act with the owner’s role and project access. Hosted MCP uses OAuth. See [Credentials](/platform/settings#api-keys) before choosing authentication.

## Follow a complete tutorial

* [GitHub localization workflow](/platform/tutorials/github-localisation-workflow)
* [React Intl and ICU](/platform/tutorials/react-intl-icu)
* [Vue i18n](/platform/tutorials/vue-i18n)
* [iOS Strings](/platform/tutorials/ios-strings)
* [Android resources](/platform/tutorials/android-string-resources)
* [Gettext POT and PO](/platform/tutorials/gettext-pot-po)
* [XLIFF](/platform/tutorials/xliff)

## Plan the delivery sequence

Upload sources, request generation, wait for the job result, review, then retrieve target files. A successful source push does not imply generation occurred. A successful job does not imply human approval.

Keep credentials in your environment or CI secret store and inspect failures before retrying a request that may create duplicate work. Use the documented public API for custom integrations; application-internal organization routes are not a supported public API contract.
