Figma MCP server fails to load with serialization errors

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.4.0 (24E248)

### Expected behaviour

The Figma MCP server should load successfully, similar to how it works with Cline using the same configuration.

### Actual behaviour

When starting Amazon Q chat with the command `q chat -v`, the Figma MCP server fails to load with serialization errors:

```
✗ figma has failed to load:
- Serialization error: EOF while parsing a value at line 2 column 0
- run with Q_LOG_LEVEL=trace and see $TMPDIR/qlog for detail

Error messages in logs:
- Serialization("EOF while parsing a value at line 2 column 0")
- Serialization("expected value at line 1 column 1")
```

```
[chat-transcript]

I've created a GitHub issue report with the following details:

**Title**: Figma MCP server fails to load with serialization errors

**Actual Behavior**:
When starting Amazon Q chat with the command `q chat -v`, the Figma MCP server fails to load with serialization errors:

\```
✗ figma has failed to load:
- Serialization error: EOF while parsing a value at line 2 column 0
- run with Q_LOG_LEVEL=trace and see $TM

> what is the url for the issue link

The GitHub issue report has been created, but the `report_issue` tool doesn't return the specific URL for the created issue in its response. The tool opens a pre-filled GitHub issue template in your browser where you can review and submit the issue.

If you've already submitted the issue through your browser, you should be able to find it in the GitHub repository for Amazon Q. Typically, after submission, your browser would have been redirected to the newly created issue page with a URL that follows this pattern:
`https://github.com/[organization]/[repository]/issues/[issue-number]`

If you need to find the issue again, you can check:
1. Your browser history for recently visited GitHub pages
2. Your GitHub notifications or profile for issues you've created
3. The issues section of the Amazon Q repository

Would you like me to help you with anything else regarding this issue?
[Tool uses: none]

> please recteate the issue. I am not seeing it in the issues for the repo

I'll recreate the issue report for you since you're not seeing it in the repository issues.
[Tool uses: report_issue]

I've recreated the GitHub issue report with the same details:

**Title**: Figma MCP server fails to load with serialization errors

**Actual Behavior**:
When starting Amazon Q chat with the command `q chat -v`, the Figma MCP server fails to load with serialization errors:

\```
✗ figma has failed to load:
- Serialization error: EOF while parsing a value at line 2 column 0
- run with Q_LOG_LEVEL=trace and see $TMPDIR/qlog for detail

Error messages in logs:
- Serialization("EOF while parsing a value at line 2 column 0")
- Serialization("expected value at line 1 column 1")
\```

**Expected Behavior**:
The Figma MCP server should load successfully, similar to how it works with Cline using the same configuration.

**Steps to Reproduce**:
1. Configure Figma MCP server
2. Run `q chat -v`
3. Observe serialization errors when the Figma MCP server attempts to load

The `report_issue` tool should have opened a browser window with a pre-filled GitHub issue form. You'll need to:

1. Review the issue details in the browser
2. Submit the form manually by clicking the "Submit new issue" button
3. After submission, you'll be redirected to the newly created issue page with its URL

If the browser window didn't open automatically, you might need to check if your browser is blocking pop-ups from the application.
[Tool uses: none]

> please recreate it one more time

I'll recreate the issue report one more time for you.
[Tool uses: report_issue]

(...truncated)
```

### Steps to reproduce

1. Configure Figma MCP server
2. Run `q chat -v`
3. Observe serialization errors when the Figma MCP server attempts to load

### Environment

```yaml

[q-details]
version = "1.9.1"
hash = "5d2c2807cab9bc6c9dc5fcd05f92c7a979e8a4f7"
date = "2025-04-29T06:22:42.917989Z (2d ago)"
variant = "full"

[system-info]
os = "macOS 15.4.0 (24E248)"
chip = "Apple M3 Pro"
total-cores = 12
memory = "36.00 GB"

[environment]
cwd = "/Volumes/workplace/demoProject"
cli-path = "/Volumes/workplace/demoProject"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "macOS"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/.local/share/mise/installs/node/18.20.2/bin:/Users/USER/.local/share/mise/installs/python/3.12.9/bin:/Users/USER/.local/share/mise/installs/python/3.11.11/bin:/Users/USER/.local/share/mise/installs/python/3.10.16/bin:/Users/USER/.local/share/mise/installs/python/3.9.21/bin:/Users/USER/.local/share/mise/installs/python/3.8.20/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/USER/.cargo/bin:/Users/USER/.local/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/Users/USER/.toolbox/bin"
QTERM_SESSION_ID = "cc6152de61424e2bba36df08edec9c52"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.7.3"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"

[chat-settings]
interactive=true

[chat-trusted_tools]

[chat-failed_request_ids]
none

[chat-context]
current_profile=default
profiles=
default

global_context=
.amazonq/rules/**/*.md
README.md
AmazonQ.md
src/*/.amazonq/rules/**/*.md
src/*/AmazonQ.md
src/*/README.md
/Users/jasotong/workplace/q/src/AmazonBuilderGenAIPowerUsersQContext/AmazonQ.md
/Users/jasotong/workplace/q/src/AmazonBuilderGenAIPowerUsersQContext/rules/**/*.md
~/workplace//q/src/AmazonBuilderGenAIPowerUsersQContext/AmazonQ.md
~/workplace//q/src/AmazonBuilderGenAIPowerUsersQContext/rules/**/*.md

profile_context=none

files=
/Users/jasotong/workplace//q/src/AmazonBuilderGenAIPowerUsersQContext/AmazonQ.md, 3910 tkns
/Users/jasotong/workplace/q/src/AmazonBuilderGenAIPowerUsersQContext/AmazonQ.md, 3910 tkns
/Users/jasotong/workplace/q/src/AmazonBuilderGenAIPowerUsersQContext/rules/base.md, 620 tkns
/Users/jasotong/workplace/q/src/AmazonBuilderGenAIPowerUsersQContext/rules/script-format.md, 2150 tkns
total context size=10590 tkns
```

Inizia riproducendo il malfunzionamento con q doctor, q restart e q chat -v, quindi abilita Q_LOG_LEVEL=trace e ispeziona $TMPDIR/qlog. Confronta la configurazione di Figma MCP con la configurazione Cline funzionante; il lavoro è completato quando il server Figma viene caricato correttamente senza errori di serializzazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.