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
42
43
44
45
46
47
48
49
//! A [Model Context Protocol](https://modelcontextprotocol.io) server for
//! BACnet sites (#2066), so an AI agent host (Claude Code, Codex and
//! others) can discover devices and read them through the same engine and
//! request limits as the `bacnet` tool's terminal UI, and, when a profile
//! opts in, write through the TUI's preview tiers, ledger and audit log
//! (#2068).
//!
//! The server is built on the official `rmcp` SDK and targets the
//! 2026-07-28 revision of the protocol, while still answering clients that
//! open with the older `initialize` handshake. `bacnet mcp serve --stdio`
//! (the CLI's `mcp` feature) runs it; `docs/design/mcp.md` has the design.
//!
//! - Every tool reaches the network only through
//! [`bacnet_ops::engine::Engine`], under its per-device gate and global
//! rate, a rate per network, and a token bucket per principal
//! ([`Policy`]). Each result reports what it cost.
//! - Device-supplied text comes back in an untrusted envelope: cleaned of
//! control and bidirectional characters, defanged and capped.
//! - Results are paged with cursors signed by a per-process key.
//! - Passive mode builds no client and lists only the tools that send
//! nothing.
//! - Writes are off by default. With `mcp_writes = "elicit"` the client's
//! confirmation may approve a T1 write and a plan grant the writes it
//! names; T2 and T3 need a verifiable approver. The confirmation state is
//! sealed for its caller, single use and short-lived.
//!
//! Stdout carries only JSON-RPC: this crate never prints, and its logs go
//! through `tracing`, which the host process points at stderr.
pub use Policy;
pub use ;