monday.com connector: reports connected + toggled on in-chat, but tools never load in Claude Chat (load fine in Cowork, same account)

[quocentric]

What happened?

The monday.com MCP connector reports "connected" at the account level and is toggled ON in the in-chat tools menu, but its executable tools (e.g. get_board_schema, get_board_items_by_name) never load in the Claude Chat surface (although they used to for several weeks, until 2-3 days ago). The same connector, same account, loads and invokes tools correctly in Cowork.

Environment

Surface that fails: Claude Chat (web)
Surface that works: Cowork (same account, same connector)
Connector: monday.com (MCP)
Plan: Max

What did you expect to happen?

Expected
Claude invokes the monday.com tool and returns board data.

Actual
Claude reports the connector's tools are not active in the session and cannot call them. No tool invocation occurs. A registry lookup confirms the connector is "connected" and lists its tools, but they are not injected into the session as callable.

Steps to reproduce

Steps to reproduce

Confirm monday.com is connected in Settings → Connectors (green/connected).
Open a fresh chat.
Confirm monday.com is toggled ON in the in-chat tools/connectors menu.
Request a live read on a board (e.g. get_board_schema for board 18417676676).

Area

Tool Discovery / Invocation

MCP Server (if applicable)

Monday.com

Error messages or logs

There is no error popup or ofid_ reference code produced — the failure is silent. The connector reports "connected" and lists its tools via registry lookup, but the tools are never injected as callable into the Chat session. When a monday.com read is requested, Claude returns (verbatim):

"I don't have that tool loaded in my current toolset, though — the monday.com connector is connected but its tools aren't active in this session. Turn on the monday.com connector for this chat (via the tools/connectors menu), and I'll pull the live read on board 18417676676 using get_board_schema."

A connector registry lookup in the same session confirms monday.com as "connected": true and lists its tools (get_board_schema, get_board_items_by_name, create_item, change_item_column_values, etc.), yet none are invocable in the Chat turn.
Note: get_board_info does not exist as a tool name; the correct read tool is get_board_schema — this was confirmed and is not the cause of the failure. The failure is that no monday.com tool loads at all in the Chat surface, while the same tools load and invoke correctly in Cowork on the same account.
No ofid_ reference ID has appeared. If one surfaces on a future attempt, it will be added.

Additional context

Notes / already ruled out

Account connection: ON
Per-chat connector toggle: ON
Fresh chat (to force tool injection at chat creation): no change
Repeated account-level re-toggling: no change
Not a tool-rename issue — get_board_schema still exists
Capability confirmed working in Cowork on the same account/connector, so the failure is isolated to the Chat surface's tool injection.

[LGSA-Platforms]

Same symptom here, separate account. monday.com connector shows Connected in Settings, all 38 tools (4 interactive, 34 read-only) set to Always Allow. tool_search returns zero monday.com tools across multiple fresh chat sessions, various query keywords tried. No error message, no ofid_ reference.

Failing since 2 July 2026, reproduced independently by two separate users on the same account. Already ruled out: reauth, full disconnect/reconnect, setting all permissions to Always Allow, testing in brand new threads.

Business-critical daily workflow blocked as a result.

possibly related to #535, similar tool-injection symptom on a different connector

[shvixxl]

Hi! We experienced the same issue with the Windsor.ai connector. Looks like the issue is caused by the dot in the connector's name: #580

Hopefully, Anthropic will fix it soon!

[quocentric]

This is causing major issues with my team... and still no reply from Anthropic to this post, or resolution to this issue?!

It was working fine for 2 months... then all of a sudden - kaput.

- Claude Max subscriber for 3 months now... and have yet to get an answer from Support on any issue reported

[LGSA-Platforms]

Update: workaround from #580 resolved this for us. Removed the original monday.com connector (had to fully delete it, not just disconnect, since the URL stays registered otherwise) and re-added it as a custom connector using the same server URL (https://mcp.monday.com/mcp) but named "monday" (no dot). Full toolset now loads, confirmed both read and write access working in a fresh thread.

Given the connector name still shows "monday.com" (with the dot) as the default when adding via the standard flow, this looks like the root cause #580 identified. Worth flagging that this affects anyone adding it the default way, not just custom setups.

[27pchrisl]

Can confirm with a different name - our service is called 'Four/Four' (with the slash). So people are guided to use that name when connecting it up. Doesn't work as 'Four/Four', does work as 'FourFour'.

So it's not just dots, it's slashes too. Just removing the slash started it working.

[localden]

Dup of #580 (as linked in the thread). Same bug: a dot in the connector name breaks tool lookup on the Chat side. #580 has the diagnosis and a workaround, tracking the fix there. Reopen with new info if you're hitting something different.