Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] Paper MCP server should not auto-launch Paper app every time on Claude Code startup [1 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#47852•Fetched 2026-04-15 06:40:30
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
kamiimeteorkamiimeteor
Participants
github-actions[bot]github-actions[bot]kamiimeteorkamiimeteor
Timeline (top)
labeled ×3commented ×1unlabeled ×1

Fix Action

Fix / Workaround

Every time I launch Claude Code (desktop app or CLI), the Paper app automatically opens and comes to the foreground, even when I have no intention of using any design tools in that session. This is disruptive to my workflow — I have to manually close or minimize Paper each time. Paper is registered as a built-in MCP server via the frontend-design plugin, and there is no user-facing setting in either Claude Code or Paper to prevent this auto-launch behavior. The only current workaround is to disable the frontend-design plugin entirely, which removes access to Paper MCP tools I do need occasionally.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Every time I launch Claude Code (desktop app or CLI), the Paper app automatically opens and comes to the foreground, even when I have no intention of using any design tools in that session. This is disruptive to my workflow — I have to manually close or minimize Paper each time. Paper is registered as a built-in MCP server via the frontend-design plugin, and there is no user-facing setting in either Claude Code or Paper to prevent this auto-launch behavior. The only current workaround is to disable the frontend-design plugin entirely, which removes access to Paper MCP tools I do need occasionally.

Proposed Solution

Lazy-initialize the Paper MCP server connection. Instead of connecting to (and launching) Paper on Claude Code startup, defer the connection until a Paper MCP tool is actually invoked during a session. This way:

  1. Starting Claude Code does NOT open Paper automatically.
  2. When I first use a Paper-related tool (e.g. get_basic_info, write_html), Paper launches at that point and the MCP connection is established.
  3. Optionally, provide a setting like "lazyMcpServers": ["paper"] in settings.json so users can control which MCPservers use lazy initialization.

This keeps full Paper functionality available on demand while eliminating the unwanted auto-launch on every Claude Code startup.

Alternative Solutions

Currently I work around this by manually closing Paper every time after launching Claude Code. The only other option is disabling the frontend-design plugin entirely in settings.json, but that removes Paper MCP tools I need for occasional design work.

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Implement lazy initialization for the Paper MCP server connection to prevent automatic launch on Claude Code startup.

Guidance

  • Defer the connection to the Paper MCP server until a Paper-related tool is invoked during a session.
  • Introduce a setting like "lazyMcpServers": ["paper"] in settings.json to allow users to control which MCP servers use lazy initialization.
  • Modify the frontend-design plugin to support lazy initialization of the Paper MCP server connection.
  • Test the lazy initialization feature with various Paper-related tools to ensure it works as expected.

Example

No code snippet is provided as the issue does not contain sufficient technical details.

Notes

The proposed solution requires modifications to the frontend-design plugin and possibly the Claude Code application. The implementation details may vary depending on the underlying architecture and technologies used.

Recommendation

Apply the proposed workaround by implementing lazy initialization for the Paper MCP server connection, as it addresses the user's concern without removing access to Paper MCP tools.

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…
#API rate limit#retriever error#indexing error#inference speed#output truncation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [FEATURE] Paper MCP server should not auto-launch Paper app every time on Claude Code startup [1 comments, 2 participants]