Summary
When a user adds tapps-mcp to their MCP config (.mcp.json or .claude/settings.json) mid-session, the tools do not appear until the session is restarted. This is expected behavior, but it's not documented and causes confusion.
Suggestion
- Add a note to README / quickstart: "After adding tapps-mcp to your MCP config, restart your Claude Code session for the tools to become available."
- Consider having
tapps-mcp init print this reminder after writing config
- The
tapps-mcp doctor output could include a note when config is present but tools weren't available in the current session
Context
From tapps-feedback.md: "tapps-mcp tools were NOT available this session. The .claude/settings.json with mcpServers config was created mid-session, but MCP servers are only connected at session start. All tapps-mcp tools are deferred to next session."
This was the #1 source of confusion during initial project setup.
Summary
When a user adds tapps-mcp to their MCP config (
.mcp.jsonor.claude/settings.json) mid-session, the tools do not appear until the session is restarted. This is expected behavior, but it's not documented and causes confusion.Suggestion
tapps-mcp initprint this reminder after writing configtapps-mcp doctoroutput could include a note when config is present but tools weren't available in the current sessionContext
From tapps-feedback.md: "tapps-mcp tools were NOT available this session. The .claude/settings.json with mcpServers config was created mid-session, but MCP servers are only connected at session start. All tapps-mcp tools are deferred to next session."
This was the #1 source of confusion during initial project setup.