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

> ## Agent Instructions
> Choose User guide for browser tasks, Developers for CLI, SDK and external agents, and Administration for organization management.
> Confirm identity and organization/project context before operations. Documentation access does not grant ThinkPlatform permissions.
> Review side effects, verify changes with a read, and do not blindly retry an operation with an uncertain outcome.
> Use documented UI steps for the web app and documented public CLI or SDK interfaces for automation. Follow each page’s prerequisites and authentication requirements.

# Registry and modules

> Find container images and inspect project integrations.

**DevOps → Registry** lists container images. **DevOps → Modules** manages project API and MCP integrations. These are separate resources: an image can be deployed to a runtime, while a module describes an integration and its endpoints.

## Find an image

1. Select the organization and project and open **DevOps → Registry**.
2. Choose **Organization** or **Common**, search for a repository and select it to load its tags.
3. Inspect the tag, digest and update time. Copy the image reference for the intended deployment and verify its image and runtime status after deployment.

Browsing an image does not prove the target runtime can pull it. If pull credentials are missing or a deployment fails, check the target's registry configuration and runtime identity with the responsible administrator.

Organization registry push requires an organization Owner or Admin; project Owner alone is insufficient. Common registry push and deletion are restricted to platform administrators. Delete controls depend on the relevant management permission. Before deleting a tag or repository, find its active deployment references and confirm the intended target: deletion can prevent future deployments or rollouts. Verify the result in the registry afterward.

## Register an MCP module

This example requires a reachable MCP server, its approved endpoint URL and any server-required authentication header. Ask the server administrator for those values and a harmless read-only tool and test input. The example URL `https://mcp.example.com/mcp` is a placeholder, not a working service.

1. Open **DevOps → Modules** and choose **Add API**. Set **Type** to **MCP**, enter `Example tools` in **API Name**, and enter the approved MCP endpoint URL.
2. If the server requires a header, use **Custom headers → Add header**, enter its **Header name** and **Header value**, and leave it enabled. Keep credentials out of prompts and shared notes. Review **Sharing settings**, then save. Complete any separate server authorization if prompted and submit again.
3. Select the saved module and inspect its discovered endpoints. Open the agreed read-only tool and use **Tool Test** to enter the benign input required by its displayed schema. Run it and inspect the result or error. Tool tests make real requests, so check the tool's effects before running one. Registration alone does not guarantee remote authorization.

If tools are missing or the test fails, verify the URL, module access, headers and external authorization with the server administrator. Saved sensitive values may be masked; enter a replacement deliberately when rotating a credential. Before deleting a module, identify its dependent agents and flows.

See [Cloud and edge operations](https://docs.thinkplatform.ai/guides/operations/cloud-and-edge.md), [Operate agent workspaces](https://docs.thinkplatform.ai/guides/operations/workspaces.md), and the [Python SDK overview](https://docs.thinkplatform.ai/python-sdk/overview.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.