
Connexion avec Amazon Q Developer
Amazon Q Developer — CLI and IDE extension, configured through mcp.json.
Ce contenu est disponible en anglais.
Quel MCP allez-vous connecter ? Les commandes ci-dessous s'adaptent à votre choix.
- 1
Generate your API key
Sign in to app.newalgorithm.io with your account, open Keys & apps and generate a key. It is shown only once: copy it and store it somewhere safe.
Key formatna_live_xxxxxxxxxxxxxxxxx - 2
Choose the configuration scope
Amazon Q reads two files: a global one, which applies in any folder, and one per workspace. Prefer the global one so the key never touches the repository.
Where the file isGlobal: ~/.aws/amazonq/mcp.json Workspace: .amazonq/mcp.json - 3
Declare the NewAlgorithm server
In versions that already support native HTTP transport, the remote server is declared directly by URL:
~/.aws/amazonq/mcp.json{ "mcpServers": { "NewAlgorithm-TOTVS": { "type": "http", "url": "https://totvs.mcp.newalgorithm.io/mcp", "headers": { "Authorization": "Bearer na_live_xxxxxxxxxxxxxxxxx" } } } } - 4
If your version only accepts stdio
Use the mcp-remote bridge — from the agent's point of view the result is identical. Requires Node.js.
~/.aws/amazonq/mcp.json (alternative){ "mcpServers": { "NewAlgorithm-TOTVS": { "command": "npx", "args": [ "-y", "mcp-remote", "https://totvs.mcp.newalgorithm.io/mcp", "--header", "Authorization: Bearer na_live_xxxxxxxxxxxxxxxxx" ] } } } - 5
Confirm with the CLI
q mcp listRésultat attendu : NewAlgorithm-TOTVS
- 6
And inside the chat
In the q chat session, the command below lists the tools loaded from each server.
/toolsRésultat attendu : na_prepare, na_search, na_route, na_specialists, na_version
The Amazon Q extension for VS Code and JetBrains reads the same mcp.json as the CLI — configure it once and it works for both. Restart q chat after editing the file: servers are loaded at startup.
Détails sur l'authentification et les outils dans la Documentation.