# Beam MCP overview

> Make Beam’s local scanning and inspection tools available to an MCP-compatible assistant.

Source: https://docs.agentbeam.com/agent-cli/mcp/overview

Beam MCP is a thin wrapper around the installed Beam CLI. It exposes five local read-only tools over standard input/output (stdio). It does not launch the collector, configure agent hooks, enroll devices, execute the scanned instructions, or install the MCP servers described in a scanned file.

## What it adds to your assistant

Use the MCP tools when an assistant needs to review supplied instruction text, inspect a local skill file, scan an MCP configuration, or understand Beam's current rule and agent catalog. A collector health tool can check an already-running loopback collector.

The MCP host chooses when and how to invoke tools under its own permission system. Results are returned to that host; a locally executed scan does not mean the host's model or conversation storage is offline.

## Tool coverage

| Tool                         | Purpose                                                    |
| ---------------------------- | ---------------------------------------------------------- |
| `beam_scan_content`          | Scan inline skill text or MCP JSON                         |
| `beam_scan_path`             | Read and scan a file already on disk                       |
| `beam_list_rules`            | List built-in, custom, and sequence rule definitions       |
| `beam_list_supported_agents` | Inspect supported adapters and payload verification status |
| `beam_collector_status`      | Check your local collector without starting it             |

See [tool reference](https://docs.agentbeam.com/agent-cli/mcp/tools) for exact inputs and limits. Scanning uses the CLI's implementation instead of maintaining a second detection engine.

## Local transport and prerequisites

Install the public CLI package `@agent-beam/beam` and make its `beam` executable available to the MCP server process. The MCP package requires Node.js 20.17 or newer and a built entrypoint. Only stdio transport is implemented in this source version; a hosted MCP endpoint is not part of this setup.

The local checkout is named `agentbeam-mcp`, while its package name is `beam-mcp`. Use the actual built path in your host configuration rather than assuming those directory names are interchangeable.

## Boundaries to keep in mind

Path scanning can read files accessible to the server process; it is not confined to a project root by the wrapper. Inline content is temporarily written to disk for the CLI scan. Apply host permissions and filesystem isolation appropriate to the material you allow the assistant to inspect.

Findings are heuristic evidence for review. None of these tools provide a malware verdict, configure enforcement, or approve connecting a server.