ferridriver-mcp 0.4.0

ferridriver MCP server library -- browser automation via Model Context Protocol
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

//! MCP tool definitions -- split by category, each with its own `tool_router`.
//!
//! Each submodule defines tools in a separate `#[tool_router]` impl block.
//! Routers are combined via `+` in `McpServer::tool_router()`.
//!
//! # Surface by category
//!
//! - **navigation** — session bootstrap: `connect`, `navigate`, `page`
//! - **content** — observation + light JS: `snapshot`, `screenshot`,
//!   `evaluate`, `search_page`
//! - **network** — session diagnostics: `diagnostics`
//! - **script** — imperative scripting: `run_script` (the action path)
//! - **extensions** — `ferridriver_extensions`: introspect loaded plugins
//!
//! Browser interaction flows through `run_script`, which exposes `page`,
//! `context`, and `request` globals over the ferridriver core.

pub mod content;
pub mod extensions;
pub mod navigation;
pub mod network;
pub mod script;

use crate::server::McpServer;
use rmcp::handler::server::router::tool::ToolRouter;

impl McpServer {
  /// Build the base tool router by combining all category routers.
  ///
  /// Stored in a field on construction so consumers can merge extra tools
  /// via `with_extra_tools()`. The `#[tool_handler]` macro dispatches
  /// through the field (`self.tool_router`) rather than calling this method.
  #[must_use]
  pub fn tool_router() -> ToolRouter<Self> {
    Self::navigation_router()
      + Self::content_router()
      + Self::network_router()
      + Self::script_router()
      + Self::extensions_router()
  }
}