[BUG] COWORK || Local / desktop MCP tools not exposed to claude cowork, all the tools work properly in claude chat

Resolved 💬 21 comments Opened Jan 23, 2026 by asaddcorp123 Closed Feb 3, 2026

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?

The tools added as local dev or via mcpb files do not work in claude desktop cowork, but work properly in claude chat. the tools added as http via custom connectors work in cowork.

What Should Happen?

All the tools regardless of how it is added to claude desktop, must work on claude cowork. everything that works on claude desktop chat, should work on claude cowork aswell.

Error Messages/Logs

Steps to Reproduce

ask claude in cowork mode to list mcp tools present and you will see the list populated only for HTTP MCPs added via custom connector. all other types of MCPS do not get listed to cowork mode, the same queries in chat mode work as expected.

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude 1.1.673 (5a47b0) 2026-01-22T18:12:14.000Z

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

21 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/18671
  2. https://github.com/anthropics/claude-code/issues/17896
  3. https://github.com/anthropics/claude-code/issues/18194

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

asaddcorp123 · 5 months ago

This issue us much more detailed, and is for local dev mcps, extensions and it clarifies what works what doesn't, and what's the difference between what works and what doesn't very clearly

poorbengunn · 5 months ago

I have identical issues, and it makes Cowork effectively pointless.

dial481 · 5 months ago

I have the same issue as recently as today with Claude 1.1.1093 (5a5517) 2026-01-27T17:57:04.000Z

#17896 was supposed to resolve this but did not.

graceclarify · 5 months ago

My node-based local MCP servers are available, but the python-based ones are not. I'm Claude 1.1.1200 (46e533) 2026-01-28T03:42:34.000Z

dial481 · 5 months ago

I'm on Claude 1.1.1200 (46e533) 2026-01-28T03:42:34.000Z now. No local MCPs work for me in Cowork. They all work in Chat.

The agent says:

The toggle shows it's enabled, but the tools aren't actually available to me. This usually means one of:
MCP server isn't actually running/connected - the toggle is on but the connection failed Session needs restart - MCPs enabled mid-session sometimes don't load until you start a new conversation Configuration issue - the MCP might not be properly configured (SSH keys, host, etc.)

EDIT: I saw there was another update pending after 1.1.1200 but the problem remains on Claude 1.1.1520 (48ced7) 2026-01-30T03:29:40.000Z

aserechenko · 5 months ago

Claude 1.1.1520 (48ced7) 2026-01-30T03:29:40.000Z

Confirm all local MCPs are gone in Cowork/Code. Available in the Chat.

cmrigney · 5 months ago

We're also experiencing issues with Docker's mcp gateway. When trying to use tools in the cowork tab, it suddenly no longer has the configured tools like it did in "chat," but it still has dynamic tools - which tells me that the gateway likely either can't read the filesystem, or it can't exec docker (or both).

alicelovescake · 5 months ago

Hey everyone, thanks for the report. We have a fix for internal servers in cowork/code tab of the desktop app that's going to be released today! Will update with the new version once we release and confirm with you guys if it's fixed. Really appreciate everyone's investigations/reports and apologize for the disruptions to your workflows!

alicelovescake · 5 months ago

Just released Claude 1.1.1890 (af393c) 2026-02-03T21:05:53.000Z can everyone update to the latest and let me know if local MCPs work in cowork and code? 🙏

jamesckemp · 5 months ago

@alicelovescake working!

alicelovescake · 5 months ago

Yayyyy! Thanks for confirming James! I am so sorry for taking 2 weeks to notice this issue. Appreciate you guys for your patience and for trying out cowork and code!

dial481 · 5 months ago

Confirmed working with Claude 1.1.1890 (af393c) 2026-02-03T21:05:53.000Z

graceclarify · 5 months ago

Unfortunately, my issues with the local Python-based MCP servers persist in Claude 1.1.1890 (af393c) 2026-02-03T21:05:53.000Z.

They are accessible in Claude Desktop but strangely not in Claude Code or Claude Cowork.

alicelovescake · 5 months ago

@graceclarify looking into the python issue

update: I think i have a fix for this. Will be in the next release probably happening on Thursday. Appreciate your patience!

graceclarify · 5 months ago
update: I think i have a fix for this. Will be in the next release probably happening on Thursday. Appreciate your patience!

Awesome, thank you!

cmrigney · 5 months ago

Confirmed the Docker mcp gateway is working again in Claude 1.1.1890 (af393c) 2026-02-03T21:05:53.000Z. Thanks!

adamlonsdale · 5 months ago

Python based ones also not working here on Version 1.1.2156 (4e9bb2)

makote · 5 months ago

On our team a local extension/connector works for people that had the dxt extension installed before cowork was released but doesn't work for the ones that are installing it after cowork was released.

graceclarify · 5 months ago

@alicelovescake Local python based mcp servers are now working for me on Claude 1.1.2156 (4e9bb2) 2026-02-05T20:04:28.000Z. Thanks.

github-actions[bot] · 5 months ago

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.