banira mcp — CLI reference

Run banira as a Model Context Protocol (stdio) server, so an AI coding assistant can introspect, verify, document and scaffold your vanilla components against banira’s real data — the manifest and actual compiler/test results — instead of hallucinating component APIs.

Usage

$ banira mcp [options]

Options

Option	Description
`--read-only`	Expose only the read/analysis tools — no file writes or scaffolding. Safe to leave always-on.
`--local-only`	Confine file access to the project (cwd or --project dir) and never emit network-reaching output (e.g. force a local doc stylesheet instead of the CDN).
`-p, --project <path>`	Path to a tsconfig.json whose options override the compiler defaults for the compile/analysis tools.

Examples

run the server

$ banira mcp

always-on, read-only

$ banira mcp --read-only

inspect it interactively

$ npx @modelcontextprotocol/inspector npx banira mcp

Notes

Add it to any MCP client's config:

{
  "mcpServers": {
    "banira": { "command": "npx", "args": ["-y", "banira", "mcp"] }
  }
}

It exposes 10 tools — introspection (get_component_manifest, get_component_api, list_components, get_component_demo), verify (check_component, compile_component, test_component), generate_docs, and authoring (get_authoring_guidelines, scaffold_component) — plus 2 resources (resource://banira/components, resource://banira/authoring-guide) and 3 prompts. It speaks newline-delimited JSON-RPC 2.0 (MCP 2025-11-25) and adds no heavy dependencies. See the MCP server guide for the full catalog and setup.