Skip to content
Oka Docs

Amazon Q Developer integration

Amazon Q Developer supports MCP servers in both its IDE extensions and CLI.

Setup (IDE)

1. Add to your MCP config

Edit ~/.aws/amazonq/mcp.json (global) or .amazonq/mcp.json (workspace):

{
  "mcpServers": {
    "oka": {
      "command": "npx",
      "args": ["-y", "@oka-core/reason"]
    }
  }
}

Workspace config (.amazonq/mcp.json) takes precedence over global.

2. Authenticate

In Amazon Q chat, use the login tool:

Use the login tool to authenticate with Oka

This opens your browser to id.oka.so where you sign in or create an account. Your credentials are stored locally and refresh automatically.

Setup (CLI)

Terminal window
qchat mcp add oka -- npx -y @oka-core/reason

Then authenticate via the login tool in a qchat session.

Verify:

Terminal window
qchat mcp list
qchat mcp status

Amazon Q-specific options

Timeouts

Set per-server tool execution timeout:

{
  "mcpServers": {
    "oka": {
      "command": "npx",
      "args": ["-y", "@oka-core/reason"],
      "timeout": 30
    }
  }
}

Tips

  • Set OKA_WORKSPACE in the env block to scope events to your project.
  • Amazon Q Pro/Enterprise users should check with their admin — MCP governance policies may restrict which servers can be used.
  • Workspace .amazonq/mcp.json is ideal for team setups — commit it to your repo and have each team member authenticate via login.