claude-code - 💡(How to fix) Fix [BUG] Claude for PowerPoint: MCP connector tools are not loaded into Claude's tool list at session start; only become available after refresh_mcp_connectors runs [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#58727Fetched 2026-05-14 03:41:01
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
1
Author
Timeline (top)
commented ×2labeled ×2unlabeled ×1

MCP-connector tools are not available to Claude on the first turn of a new Claude for PowerPoint session, even when the connector is connected and enabled. Claude ignores the MCP server entirely and falls back to built-in tools.

The tools only become visible after the user manually types "refresh Acme MCP tools", which triggers refresh_mcp_connectors. This is an undocumented workaround users shouldn't need to know.

Error Message

  • #27193 — "Tool names must be unique" error on first message

Root Cause

MCP-connector tools are not available to Claude on the first turn of a new Claude for PowerPoint session, even when the connector is connected and enabled. Claude ignores the MCP server entirely and falls back to built-in tools.

The tools only become visible after the user manually types "refresh Acme MCP tools", which triggers refresh_mcp_connectors. This is an undocumented workaround users shouldn't need to know.

Fix Action

Fix / Workaround

The tools only become visible after the user manually types "refresh Acme MCP tools", which triggers refresh_mcp_connectors. This is an undocumented workaround users shouldn't need to know.

MCP connector tools should be fetched and merged into Claude's tool list before the first user message is processed, so they are available on turn 1 without any manual refresh.

RAW_BUFFERClick to expand / collapse

Summary

MCP-connector tools are not available to Claude on the first turn of a new Claude for PowerPoint session, even when the connector is connected and enabled. Claude ignores the MCP server entirely and falls back to built-in tools.

The tools only become visible after the user manually types "refresh Acme MCP tools", which triggers refresh_mcp_connectors. This is an undocumented workaround users shouldn't need to know.

Environment

  • Product: Claude for PowerPoint add-in
  • Host: PowerPoint on Windows (Microsoft 365 desktop)
  • Model: Claude Opus 4.7 / Sonnet 4.6 (both affected)
  • Plan: Enterprise
  • MCP server: Custom .NET 10 server, Streamable HTTP, tools.listChanged = true

Steps to Reproduce

  1. Register and enable a custom MCP connector ("Acme MCP") in the Claude for PowerPoint connector settings.
  2. Close and reopen the Claude task pane to start a fresh session.
  3. Send a request that matches a tool on the MCP server (e.g. "update all links").
  4. Observe that Claude ignores the MCP connector and uses only built-in tools, then fails.
  5. Send "refresh Acme MCP tools" — Claude calls refresh_mcp_connectors and confirms "Acme MCP is connected."
  6. Re-send the original request — Claude now correctly calls the MCP tool and completes the task.

Expected Behaviour

MCP connector tools should be fetched and merged into Claude's tool list before the first user message is processed, so they are available on turn 1 without any manual refresh.

Actual Behaviour

MCP tools are lazy-loaded and absent on turn 1. Claude ignores the connector and fails to complete requests it could handle, requiring users to manually trigger a refresh first.

Proposed Fix

At session start (or when a connector is toggled on), call tools/list before the first user message is sent. If the server declares tools.listChanged = true, also register a notifications/tools/list_changed handler. As a minimum, run refresh_mcp_connectors implicitly at session start.

Related Issues

  • #13646 — MCP tool list not refreshed on notifications/tools/list_changed
  • #27193 — "Tool names must be unique" error on first message

Contact

Reporter: Larry — happy to provide server logs or a screen recording on request.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING