Test the packaged production connection with a read-only list-projects call before debugging any write. The default endpoint is http://localhost:16472/mcp and requires the desktop app to remain open.
Open Misaki Studio desktop and keep it running.
Confirm the URL includes http://, port 16472, and /mcp.
Reconnect or restart the MCP client.
Confirm another process did not occupy the default port.
The app can bind the next free port when 16472 is occupied, while a client configured for 16472 continues calling the old address. Free the port and relaunch, or use the actual bound port. Do not switch to a repository development server unless you intentionally want its separate environment.
The server is reachable but cannot resolve a local profile. Sign in once through the desktop app on that machine, reconnect, and call list-projects again.
The connection works, but this MCP session has no selected project. Call list-projects, identify the exact project, then select-project. Visible editor selection does not select the MCP project.
If the message returns after an app/server restart or development hot reload, select the project again before retrying. Do not assume the previous target is still active.
The MCP HTTP server answered, but the host-assisted app connection needed for Preview, capture, export, or a similar operation is unavailable. Keep the desktop app open, wait for its project host to be ready, confirm the selected project, and retry the read-only reproduction.
Reconnect the MCP client so it reloads the current server schemas. Do not infer support from an older prompt, transcript, fixed tool count, or a development-only dev-* operation.
The current endpoint has no separate MCP authentication prompt or token. Do not forward, tunnel, proxy, or expose it. Connect only trusted clients and require explicit review before deletion, export, publication, or external writes.