Noxgild

Amazon Q Developer

Connect Amazon Q Developer to Noxgild, verify protected tool access, and run a real task.

Keep legacy Amazon Q Developer workflows understandable while AWS transitions agentic development toward Kiro.

Setup tutorial

1. Choose the supported AWS workflow

  • For new AWS agent development, use Kiro and its dedicated Noxgild integration guide.
  • Amazon Q Developer is a legacy/transition path. This page does not claim an independently certified remote HTTP MCP connection.

Open Kiro guide

2. If your existing Amazon Q client supports remote MCP

  • Open its MCP server settings and check whether remote Streamable HTTP and authentication are supported.
  • Only then use the Noxgild production endpoint and the authentication method available in that client. If the option is missing, use Kiro instead.
https://mcp.noxgild.com/mcp

Before you start

  • Amazon Q Developer is presented as a transition path, not a newly certified primary client.

Noxgild MCP endpoint

https://mcp.noxgild.com/mcp

Verification prompt

Send this to your AI client after setup:

Show my Noxgild computers and verify my current development environment.

After authorization, send the verification prompt. You are connected when your authorized computer and its status appear.

Good first tasks

  • Inspect my development environment and verify the current deployment.

Troubleshooting

  • Provider product availability can change; use the Kiro guide for the current AWS agent workflow when possible.

Connect a computer once

If you do not already have an authorized Windows, macOS, or Linux computer in Noxgild, run this in a terminal on that Windows, macOS, or Linux computer:

npx @noxgild/cli@latest connect

After approval, the same computer can be reused from other supported AI clients.

On this page