Other clients - Amazonomics

Any MCP client can connect if it supports:

The Streamable HTTP transport.
OAuth with dynamic client registration. You sign in through the browser, so the client needs no stored credentials.

Point the client at:

https://mcp.amazonomics.com/mcp

Most clients accept a JSON configuration like this:

{
  "mcpServers": {
    "amazonomics": {
      "url": "https://mcp.amazonomics.com/mcp"
    }
  }
}

Clients without HTTP support

Some clients only run local MCP servers over stdio. For those, bridge the connection with mcp-remote:

{
  "mcpServers": {
    "amazonomics": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.amazonomics.com/mcp"]
    }
  }
}

Discovery details

For clients that read OAuth metadata:

Document	URL
Protected resource metadata	`https://mcp.amazonomics.com/.well-known/oauth-protected-resource`
Authorization server	`https://amazonomics.com/.well-known/oauth-authorization-server`

The search tools need the amazonomics:search:read scope. Clients that follow the MCP authorization specification discover all of this from a 401 response, without configuration.

Troubleshooting

The client reports 401 after login. Sign out of the client’s connection and connect again. Tokens expire. Most clients refresh them without help.
The client reports 403 with a plan message. MCP access needs an active Pro or Studio subscription.
The client cannot find the server. Make sure that the URL is https://mcp.amazonomics.com/mcp, not the API hostname.

​Clients without HTTP support

​Discovery details

​Troubleshooting

Clients without HTTP support

Discovery details

Troubleshooting