From Lovable you can build against live Amazon data while you are still designing the app — pull real campaign, order, and catalog data into the chat as you iterate, so the interface you ship is shaped by what your Seller Central and Ads accounts actually return rather than by placeholder JSON.
One thing to know before you start: a custom MCP server in Lovable is a chat connector. It is personal to your account and is never part of your published app. It shapes what you build; it is not a runtime dependency your users inherit. If the app itself needs Amazon data at runtime, that is a server-side integration you build, not this connector.
Your MCP server hostname is private to your deployment. It comes from your cloud provider, belongs to your environment, and is not shared across customers. Replace {your-private-mcp-host} with the private host shown in your dashboard.
For the official reference, see Custom MCP in the Lovable docs.
Prerequisites
- A Lovable account. Custom MCP servers are available on all plans.
- A dashboard API key from the Keys tab, unless your deployment fronts the server with OAuth.
- The private MCP endpoint assigned to your deployment.
https://{your-private-mcp-host}/mcp1. Open the custom MCP form
Open the Connectors dashboard. Scroll to the bottom of the All view and choose the Custom card labelled MCP — "Connect your own MCP".
2. Add the server
The form takes two fields:
| Field | Value |
|---|---|
| Server name | A descriptive identifier you will name in chat, such as Kuudo Amazon. |
| Server URL | Your private MCP endpoint, https://{your-private-mcp-host}/mcp. |
Then pick how Lovable authenticates:
| Method | Use when |
|---|---|
| OAuth (default) | Your deployment fronts the MCP server with OAuth. Click Add & authorize and complete the flow. |
| Bearer token or API key | The usual path for a Kuudo dashboard key. |
| No authentication | Only for a server that requires no credentials. |
Pick a server name you will actually type. You name the connector in the prompt, so Kuudo Amazon reads better mid-sentence than mcp-prod-1.
3. Verify the connection
Ask for something only the connector can answer, naming it directly:
Using the Kuudo Amazon connector, list my five most recent orders.If the connector is live, the answer comes back from your account rather than from a guess. Start with reads before letting it write anything.
Sharing and governance
Chat connections are per-user. A colleague opening the same project sees the connector suggested but has to connect their own. There is no shared workspace credential, which is usually what you want for Amazon access — each person's calls run under their own key.
Workspace admins can turn the whole capability off under Connectors → Admin settings → Chat connectors. If the Custom MCP card is missing entirely, check there first.
Troubleshooting
The connector works in chat but not in the published app
That is the documented behaviour, not a bug. Chat connectors are personal and never ship with a published app. Build the runtime integration server-side if your users need Amazon data.
A teammate cannot see the data
Connections are per-user. Have them add the connector under their own account with their own key.
The Custom MCP card is not there
A workspace admin has disabled chat connectors, or you are looking above the bottom of the All view — the Custom card sits at the end of the list.
Unauthorized errors
Confirm the key belongs to the same workspace as the MCP server, and that you chose Bearer token or API key rather than leaving the form on OAuth.
Start using tools
Read-only prompts first:
- "Using the Kuudo Amazon connector, show my top 10 ASINs by units last week."
- "Pull current inventory levels so I can shape the low-stock view."
- "What campaign metrics are available? I want to design a dashboard around them."
Building a view against the real shape of your data is the point — it saves the round trip where the mock schema and the live response disagree.