Amazon Q Developer CLI

Stdio only — so this goes through the bridge, in either a global or a per-workspace config file.

Setup

1. Create a key in the console and export it as UNZOI_KEY.
2. Add the block below to ~/.aws/amazonq/mcp.json to make it available in every project, or to .amazonq/mcp.json for just this one.
3. Restart the CLI session.
4. Ask something that needs current reporting and check the tool call in the response.

{
  "mcpServers": {
    "unzoi": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.unzoi.com/mcp",
        "--header", "x-api-key:${UNZOI_KEY}"
      ],
      "env": { "UNZOI_KEY": "nai_your_key_here" }
    }
  }
}

What differs here

• Amazon Q Developer CLI only launches MCP servers over stdio — there is no url form, so every remote server, not only this one, goes through a bridge like mcp-remote.
• Global and workspace configs are merged. A server name defined in both is resolved in favour of the workspace entry, with a warning printed rather than an error.
• Keep the key in the env block rather than inlining it in args — args are more likely to end up in a shell history or a process list than an environment variable is.

Next

• Get a key at console.unzoi.com, if you have not.
• The tool reference — what the model is reading when it chooses between the 18 tools.
• Stories for context windows — the one habit that most changes how well an agent works against this API.
• Limits — an agent that loops can spend a month's credits faster than you expect.
• Amazon Q Developer CLI's own MCP documentation — authoritative for anything about the client itself, including config paths, which move.

Endpoint, for copying: https://api.unzoi.com/mcp