> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools.md).
# Additional Tools in Patch My PC Cloud Deployments
*Applies to: Patch My PC Cloud*
Patch My PC (PMPC) Cloud deployments include standard default settings. However, you can also add additional settings.
These optional settings are grouped into a series of related *Additional Tools*, which can be added (and, if needed, removed) to a deployment.
To add one or more optional Additional Tools to a deployment, click **Add** in the **Additional Tools** section, then select the relevant tool from the pop-up to add it to the list of **Additional Tools**.
{% hint style="success" %}
**Tip**
You can check the checkboxes beside multiple tools to add them to the list of **Additional Tools**. You can also click the **X** beside an additional tools you want to remove from the list.
{% endhint %}
Any settings you configure for a deployment will be used for the current deployment and automatically applied to any new versions of the deployment as it's updated.
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab.md) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.patchmypc.com/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
