// MCP TOOL REFERENCE

MYOPERATOR TOOLS

9 tools from the Myoperator MCP Server, categorised by risk level.

READ TOOLS

get-component-accessibility Get accessibility guidelines and requirements for a myOperator UI component get-component-examples Get React code examples for a myOperator UI component get-component-metadata Get detailed metadata for a myOperator UI component including props, variants, and dependencies get-component-source Get the full source code for a myOperator UI component (copy/paste ready) get-installation-info Get installation instructions and npm package info for myOperator UI init-project Initialize a project for myOperator UI components (runs: npx myoperator-ui init) list-components List all available myOperator UI components with their descriptions list-design-tokens List design tokens (colors, spacing, radius, typography) from the myOperator UI design system

WRITE TOOLS

install-component Install myOperator UI components using natural language or component names. Examples: - "add button" - installs button component - "add a login fo... 3/5

// FAQ

How many tools does the Myoperator MCP server have? +

The Myoperator MCP server exposes 9 tools across 2 categories: Read, Write.

How do I enforce policies on Myoperator tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Myoperator server.

What risk categories do Myoperator tools fall into? +

Myoperator tools are categorised as Read (8), Write (1). Each category has a recommended default policy.

Enforce policies on Myoperator

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →