> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/dino-ai/mcp-server/amazon-quick.md).

# Amazon Quick

This guide is about how to setup Paradime MCP remote server for Amazon Quick. Amazon Quick does not support Dynamic Client Registration (DCR) and Well-known URI discovery uses the server root path only. Path-specific metadata locations (path-insertion discovery) are not supported.

As a result, we have to follow a different setup approach explained below.

#### Step 1 - Generate an MCP Token in Paradime

In Paradime, navigate to <https://app.paradime.io/settings/api-keys> and generate an MCP token and note the MCP endpoint and the PAT token and keep them saved in a safe place, as you won't be able to see it again.

#### Step 2 - Create a MCP Connection in Amazon Quick

Navigate to the Amazon Quick homepage and click on "Connectors" on the left panel.

<figure><img src="/files/6DciYciNXjOuXobKUo5k" alt=""><figcaption></figcaption></figure>

#### Step 3 - Create Model Context Protocol connector

Navigate to Connectors -> Create for your team

<figure><img src="/files/b6WhsDtq8NdS37v3mXUc" alt=""><figcaption></figcaption></figure>

#### Step 4 - Setup a Paradime MCP

Enter a name for the MCP, and add the MCP endpoint url that we got from Step-1, and click Next

<figure><img src="/files/5QcJniDc4ToHbFupjh4C" alt=""><figcaption></figcaption></figure>

#### Step 5 - Add Authentication Details

Visit the following URL to get your connection details:

`<mcp-endpoint-url>/setup` and click **Generate Configuration**

<figure><img src="/files/r3M6i5maox1tVvBL3iji" alt=""><figcaption></figcaption></figure>

You will see all the generated details as follows:

<figure><img src="/files/o8XKVK2D4Krir6edIE5p" alt=""><figcaption></figcaption></figure>

Enter the following details from the generated configuration as follows:

* **OAuth Configuration** - choose "Custom user based OAuth"
* **Client ID** - enter `paradime-mcp-public`
* Client Secret - leave it empty
* **Token Url** - copy the token url from the generated configuration
* **Authorization Url** - copy the authorization url from the generated configuration

Once you have entered the details, click **Create and continue**

<figure><img src="/files/WPPqtbCQe0Bx3GcVk9Y5" alt=""><figcaption></figcaption></figure>

#### Step 6 - Authenticate MCP with Paradime

You will be redirected to the MCP authorization page on Paradime, where you will need to enter the MCP PAT token you saved from step 1 to authorize and then the connection will be complete.

<figure><img src="/files/Mt7aKXsEZREtY72zo5M4" alt=""><figcaption></figcaption></figure>

#### Step 7 - Connection Complete

If Step 6 was successful, you will be redirected back to Amazon Quick and you will see the following screen and click **Next** to finish.

<figure><img src="/files/xYsJ2dJxeDGDcQ0OLY31" alt=""><figcaption></figcaption></figure>

#### Step 8 - Verify MCP Tools

Once everything is done, you can go to Connectors > Search "paradime", and you should see the Paradime MCP connector. Click on it and you will find all the tools available for the MCP.

<figure><img src="/files/xZYIK7K0ETMEye3dbqDb" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/products/dino-ai/mcp-server/amazon-quick.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.