[FEATURE] Paper MCP server should not auto-launch Paper app every time on Claude Code startup

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] 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.

1. 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_