> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/9.3-install/pentaho-installation-overview-cp/installation-of-the-pentaho-design-tools/install-the-pdi-tools-and-plugins/perform-a-manual-installation-of-the-pdi-client-utilities-and-plugins/install-pdi-plugins/visit-the-pdi-marketplace-to-install-the-pdi-plugins.md).

# Visit the PDI Marketplace to install the PDI plugins

1. Start Pentaho Data Integration (PDI).
2. Select **Tools** > **Marketplace**.

   The PDI Marketplace window appears.
3. The name of the plugin appears in the **Detected Plugins** section of the page.

   Note which plugins are installed. You can filter the list by typing the name of the plugin in the **Detected Plugins** text box.
4. Click the name of the plugin to expand it.

   Information about the plugin, including the documentation, source code, and support information appears.
5. Click **Install this plugin**.

   The **Progress Information** dialog box appears, indicating the operation is in process. When the plugin has been successfully installed, a message appears indicating that you will need to restart your client, which is the PDI client (Spoon).
6. Click **OK**.
7. Restart PDI.
8. To verify that the plugin was installed, open the PDI Marketplace window again.

   The plugin should be listed as installed.

The plugin should appear in the logical place in the PDI client interface. For example, if the plugin that you install is the 'CMIS Input' plugin, then it will appear in the **Design** tab within the **Output Steps** category.


---

# 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.pentaho.com/install/9.3-install/pentaho-installation-overview-cp/installation-of-the-pentaho-design-tools/install-the-pdi-tools-and-plugins/perform-a-manual-installation-of-the-pdi-client-utilities-and-plugins/install-pdi-plugins/visit-the-pdi-marketplace-to-install-the-pdi-plugins.md?ask=<question>&goal=<user_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.
