MCP not getting configured

**Describe the bug**
The beta version was able to successfully configure the mcp but when I updated to v1 im getting issues
ng": "Let me check what MCP tools are available. The user mentioned there's a Sentry MCP server configured. Let me look at the configuration again - it should be `mcp-server-sentry`. Let me try to use it directly to get the issue details.\n\nActually, I should check if there are any MCP tools available. Let me look at the environment to see what's configured.\n\nFrom the instructions, I can see there's an MCP config for Sentry:\n```\n\"sentry\": {\n \"command\": \"pipx\",\n \"args\": [\"run\", \"mcp-server-sentry\", \"--auth-token\", \"...\"],\n \"env\": {\n \"SENTRY_AUTH_TOKEN\": \"...\",\n },\n}\n```\n\nHowever, I don't see any MCP tools in my available tools list. This means I might need to use the Sentry API directly or web-based approach.\n\nLet me try to fetch the Sentry issue data using the Sentry web interface or API. The issue ID is 6915822531.",
"signature":

```
claude_args: |
--model claude-sonnet-4-5-20250929
--allowedTools mcp__sentry__*,mcp__sentry__get_sentry_issue,Read,View,Bash,Edit,Create,Write,str_replace_editor
--mcp-config '{
"mcpServers": {
"sentry": {
"command": "pipx",
"args": ["run", "mcp-server-sentry", "--auth-token", "${{ secrets.SENTRY_AUTH_TOKEN }}"],
"env": {
"SENTRY_AUTH_TOKEN": "${{ secrets.SENTRY_AUTH_TOKEN }}"
}
}
}
}'
```

**To Reproduce**
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Workflow yml file**
If it's not sensitive, consider including a paste of your full Claude workflow.yml file.

**API Provider**

[ ] Anthropic First-Party API (default)
[ ] AWS Bedrock
[ ] GCP Vertex

**Additional context**
Add any other context about the problem here.