aws / aws/aws-toolkit-vscode

Q Dev Plugin Not Working with Miro MCP

Open
#8,512 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

## Problem

Both Visual Studio Code and IntelliJ Q Dev plugins do not work with the Miro MCP server. The issue is with the OAuth scope.

Error
```
MCP: server 'miro-mcp' failed to connect (OAuth): MCP: OAuth failed: OAuth client registration failed: HTTP 400@https://mcp.miro.com/register — {"error":"invalid_client_metadata","error_description":"Requested scopes are not valid: offline_access, openid"}
```

## Steps to reproduce the issue

Follow instructions here https://developers.miro.com/docs/connecting-miro-mcp-to-ai-coding-tools#amazon-q-ide-extension
set http MCP server to https://mcp.miro.com/

## Expected behavior

Connect to Miro MCP server to authenticate.

This could be resolved by setting, "oauthScopes": [], in the amazonq mcp.json file, however, when the save button is hit, which is a requirement to being authentication, any custom changes to the MCP server are reset.

Note that this was fixed in the CLI back in September https://github.com/aws/amazon-q-developer-cli/pull/2925

## System details (run `AWS: About` and/or `Amazon Q: About`)

- OS: Windows
Version: 1.100.2 (system setup)
Commit: 848b80aeb52026648a8ff9f7c45a9b0a80641e2e
Date: 2025-05-14T21:47:40.416Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
- AWS Toolkit version:
3.93.0
- Amazon Q version:
1.107.0

Contributor guide

Open the contributing guide

Research direction

Start with the Amazon Q MCP configuration and save flow described in the issue, then compare the VS Code and IntelliJ plugin behavior with the CLI fix in PR #2925. Reproduce against https://mcp.miro.com/ using the linked Miro MCP instructions; done means authentication succeeds and saving the server configuration no longer removes the required OAuth scope setting.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.