Add alert handling tools to server

[dhivakaranthonydoss7-eng]

Alert Handling
JavaScript alerts: Accept or dismiss alert dialogs
Confirmations: Handle confirm dialogs programmatically
Prompts: Send text to prompt dialogs
Text extraction: Get alert message content

Summary by CodeRabbit

• New Features

  • Added browser dialog handling: accept/dismiss alerts and confirmations, read dialog text, and send responses to prompt dialogs.

• Bug Fixes

  • Resolved server startup connection issue to ensure the service connects correctly at launch.

[coderabbitai]

Walkthrough

Four new browser alert/modal handling tools were added to the server: accept_alert, dismiss_alert, get_alert_text, and send_alert_text. Each interacts with the browser driver to act on the active alert and returns structured success or error responses. A commented-out server connect line was restored to enable startup connection.

Changes

Cohort / File(s)	Summary
Alert/Modal handling methods src/lib/server.js	Added four new methods: accept_alert (accepts active alert/confirm/prompt), dismiss_alert (dismisses active alert), get_alert_text (reads active alert text), and send_alert_text (sends text to a prompt then accepts). Each method switches to the alert via the browser driver, performs the action, and returns a structured content or error message.
Server startup fix src/lib/server.js	Replaced a stale commented/incorrect line with await server.connect(transport); so the server connects at startup.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    participant BrowserDriver
    Note over Server,BrowserDriver #e6f7ff: New alert/modal handling flow
    Client->>Server: request (accept_alert / dismiss_alert / get_alert_text / send_alert_text)
    Server->>BrowserDriver: switchTo().alert()
    alt alert present
        Server->>BrowserDriver: perform action (accept / dismiss / getText / sendKeys+accept)
        BrowserDriver-->>Server: result / text
        Server-->>Client: { type: "output", content: { text: result, status: "success" } }
    else no alert / error
        BrowserDriver-->>Server: throws error
        Server-->>Client: { type: "output", content: { text: error.message, status: "error" } }
    end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Verify correct use of the browser driver's alert API (switchTo().alert(), getText, accept, dismiss, sendKeys).
• Ensure consistent error handling and response formatting across all four methods.
• Confirm the restored await server.connect(transport); is placed correctly and has no side effects.

Poem

🐰 I hopped through code where pop-ups hide,
I nudged them gently, opened wide.
Accept, dismiss, or whisper text,
No modal left to vex or vexed.
A tiny rabbit, fixes next! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Add alert handling tools to server" accurately and concisely summarizes the primary change in the changeset. The main alteration is the addition of four new alert/modal handling methods (accept_alert, dismiss_alert, get_alert_text, and send_alert_text) to the server, which aligns directly with the title's intent. The title is specific and clear enough that a teammate reviewing the pull request history would immediately understand the purpose of the change, without using vague terminology or unnecessary noise. While there is a minor bug fix related to server connection, the title appropriately focuses on the primary change, which is consistent with the expectation that titles don't need to cover every detail of the changeset.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 80190fd and 9d0ae35.

📒 Files selected for processing (1)

• src/lib/server.js (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/lib/server.js

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 4

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9c1d066 and 80190fd.

📒 Files selected for processing (1)

• src/lib/server.js (2 hunks)

🔇 Additional comments (1)

src/lib/server.js (1)

564-564: LGTM! Critical fix for server connection.

This ensures the server properly connects to the transport at startup, which is essential for the MCP server to function.