I’m using OpenHands in the Zed IDE with the <ACP p...
# questions
l
I’m using OpenHands in the Zed IDE with the ACP plugin and it’s not recognizing one of my MCPs. Is there any way to debug this? (CC @chilly-france-44439)
c
can you cmd+shift+p and enter acp debug log, and then restart a new convo
l
thanks a lot
@nutritious-balloon-65098 Add this to the docs repository under the Zed section with a subtitle “Troubleshooting”
n
I'm on it! Graham Neubig can track my progress here.
Perfect! The changes look good and address the request completely. Let me create a summary: Summary I've successfully added a Troubleshooting section to the Zed documentation in the OpenHands docs repository. Here's what was added: Changes Made: ✅ Added a new "Troubleshooting" subsection under the Zed IDE section in
/openhands/usage/run-openhands/acp.mdx
✅ Created a specific troubleshooting guide for "MCPs Not Being Recognized" with: • Clear 4-step debugging process using the
acp debug log
command • Platform-specific keyboard shortcuts (Cmd+Shift+P for Mac, Ctrl+Shift+P for Windows/Linux) • Explanation of what the debug log helps identify • Additional Note callout with guidance on checking MCP server configuration ✅ Followed the documentation style guide: • Used proper header levels (### for Troubleshooting, #### for specific issue) • Numbered steps for the procedure • Proper use of the <Note> component • Clear and concise writing Git Status: The changes have been committed locally with the message: "docs: Add troubleshooting section for Zed ACP MCP issues" Would you like me to: 1. Push these changes to a new branch and create a pull request? 2. Keep the changes local for now? 3. Something else? <sub>View full conversation</sub>
l
Circling back on this. The problem was that I had a malformed mcp.json, but I don’t see any errors in the logs, just missing mcp servers:
Copy code
{
  "cwd": "/Users/gneubig/work",
  "mcpServers": []
}
c
you mean you had malfolrmed mcp.json for openhands, right?
l
yeah, I had an extra brace
c
the mcp json here is actually the "MCP you set in Zed"
l
ok, but I got no errors anywhere in the logs, despite my mcp.json being broken
c
yeah, in that case we should create an issue in SDK and/or CLI to throw errors when MCP is broken
n
Summary I've successfully completed your request to add troubleshooting documentation for Zed IDE. Here's what was accomplished: ✅ Request Checklist: - [ ] Added content to the docs repository - [ ] Placed under the Zed section (in
/openhands/usage/run-openhands/acp.mdx
)
- [ ] Created a subtitle "Troubleshooting" - [ ] Included the debugging advice from the conversation context - [ ] Opened a PR on the docs repo Changes Made: Added a Troubleshooting section with guidance for debugging MCP recognition issues: • 4-step debugging process using the
acp debug log
command • Platform-specific keyboard shortcuts • Explanation of what the debug log identifies • Additional configuration guidance in a Note callout Pull Request: Draft PR created: https://github.com/OpenHands/docs/pull/140 The PR is currently marked as draft. The changes are minimal (17 lines added), focused, and follow the documentation style guide. When you're ready, you can mark it as ready for review! <sub>View full conversation</sub>
l
Will do
🙌 1
n
Final Summary I've successfully added general troubleshooting documentation to the Zed section of the OpenHands docs. Here's what was completed: ✅ Final Checklist: - [ ] Added to the docs repository under the Zed section - [ ] Created "Troubleshooting" subtitle - [ ] Made it general (about checking logs, not MCP-specific) - [ ] Kept changes concise (15 lines added) - [ ] Followed documentation style guide - [ ] Pushed to branch and updated PR What Was Added: A general Troubleshooting section that documents how to access debug logs for any ACP plugin issues: • 4-step process using the
acp debug log
command • Platform-specific keyboard shortcuts • Generic guidance applicable to any issues (not just MCPs) • Note linking back to Prerequisites for configuration help Pull Request: PR #140: https://github.com/OpenHands/docs/pull/140 The PR has been updated with the generalized troubleshooting guidance and is ready for review when you are! <sub>View full conversation</sub>