[BUG] Claude Desktop MCP prompts fail account-wide: "Failed to attach prompt"
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Environment:
- Platform: Claude Desktop (Windows)
- Claude Version: [check Help → About]
- MCP Server: BigQuery-Assets (npx q1x3nl4g)
Bug Description:
MCP prompts suddenly stopped working on [today's date] for my account only. 4 other test accounts work fine with identical configuration.
Symptoms:
- Error: "Failed to attach prompt. You can try again."
- MCP tools: ✅ Working perfectly
- MCP prompts: ❌ Failing
- MCP resources: ❌ Failing
- Tested on multiple computers: Same result
- Worked yesterday, broke today
- No code or config changes
What Should Happen?
Expected Behavior:
Prompts should attach and generate messages like they do for other accounts.
Actual Behavior:
Prompt attachment fails with generic error. Backend appears to be rejecting prompt requests for this specific account.
Additional Context:
This appears to be an account-level backend state corruption issue, as:
- Same MCP server works for other accounts
- Same computer works for other accounts
- Multiple computers fail for this account
Error Messages/Logs
- Failed to attach prompt. You can try again.
- Failed to attach resources. You can try again.
and here in Claude > logs > window:
2025-10-03 17:33:41 [error] Potential permissions policy violation: payment is not allowed in this document.
2025-10-03 17:33:43 [error] Potential permissions policy violation: payment is not allowed in this document.
Steps to Reproduce
- Publish my MCP server to npm.
- Called it in claude_desktop_config.
{
"mcpServers": {
"BigQuery-Assets": {
"command": "npx",
"args": [
"-y",
"server-name"
],
"env": {
"BIGQUERY_PROJECT": "My biguquery project",
"BIGQUERY_KEY_FILE": "path to service account key"
}
}
}
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
claude desktop latest version
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
10 Comments
I am having the same issue "Failed to attach prompt. You can try again.".
OS: Mac
Claude Desktop.
Regression:
Yes, this is a regression.
This was working day before yesterday.
Yesterday, it worked intermittently and towards the end of the all my MCP server prompts stopped loading with the above error.
Tools work fine.
I see the below error in the MCP server log:
[5758] [Remote→Local] 6
[2025-10-03T15:12:19.909Z][5758] [Remote→Local] 6
[2025-10-03T15:12:19.910Z][5758] Remote → Local message {
method: undefined,
id: 6,
result: 'result-present',
error: undefined
}
But, I do see in the logs the server returning the content of the full prompt text
[info] Message from server: {"jsonrpc":"2.0","id":6,"result":{"description": "......<full prompt text comes here>...>" }}]}} { metadata: undefined }
MCP Tools working.
Model: Sonnet 4.5
Claude 0.13.37 (bfd4ed) 2025-09-24T22:18:50.000Z
Same happening with me, as well, with multiple MCP servers that provide prompts, including
everything. Was working yesterday, not today. Claude Desktop on Mac 0.13.37, Sonnet 4.5. Also see the prompt returning in the logs.Could it be related to the latest outage, I wonder?
https://status.claude.com/ status shows green now.
Yup, but very coincidental...
I wish I knew a way to peg Claude Desktop to a known release number so I could continue development. Except the model, which is remote, everything else is running on my desktop (claude desktop, mcp server, etc)
I didn't even update my client. No changes on my end and things just started failing.
Same issue here, MacOS 26.0.1, Claude Desktop Version 0.13.37, using local MCP server: claude-prompts-mcp. Error "Failed to attach prompt. You can try again"
Just started working for me again. No changes made on my end.
Everything is now working as expected. Thank you all for your comments and support.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.