docs(mcp-server): update tool and resource listings

[masnwilliams]

TL;DR

Updates the MCP Server reference documentation to reflect the latest available tools and resources.

Why we made these changes

To ensure our documentation is accurate and up-to-date for developers using the MCP Server API. Outdated information about available tools and resources can lead to integration errors and confusion.

What changed?

• Modified reference/mcp-server.mdx to update the lists of supported tools and resources.
• Added entries for newly available API tools.
• Removed deprecated or outdated listings.

^{Description generated by Mesa. Update settings}

[mesa-dot-dev]

Performed full review of a06ba3a...2847f29

Analysis

1. The PR focuses primarily on documentation updates rather than actual implementation of the new browser profile management capabilities, which may create a mismatch between documented features and actual functionality.

2. Adding persistent profile management introduces potential security and privacy concerns that aren't addressed in the architectural description, particularly regarding how user data is stored and protected.

3. The expansion of server functionality beyond basic browser automation represents a significant scope increase that could impact server performance, resource utilization, and maintenance complexity.

4. The PR description lacks details on how these new capabilities integrate with the existing codebase architecture, potentially leading to inconsistent implementation patterns.

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

• Configure your agents

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{1 files reviewed | 3 comments | Review on Mesa | Edit Reviewer Settings}

[mesa-dot-dev]

The resources section could benefit from more detailed explanations. Consider adding example URIs (e.g., 'profiles://profile-name' or 'browsers://browser-id') to show users the expected format for accessing specific resources.
_{Agent: 🤖 General}

[mesa-dot-dev]

The example shows using delete_browser to save a profile, but this might be confusing. Consider clarifying that this closes the setup session and saves the profile, or mention if there's a dedicated save/finalize step.
_{Agent: 🤖 General}

[dprevoznik]

LGTM - I'd consider in the future beginning to separate out this long page into separate shorter pages within the MCP section. e.g. Setup & Clients, Tools & Resources, Help & Examples