// MCP TOOL REFERENCE

JSX NOTATION TOOLS

4 tools from the Jsx Notation MCP Server, categorised by risk level.

READ TOOLS

decode_jsxn Decodes JSXN compact notation back into standard JSX/TSX or HTML source code. Use "snippet" mode for JSXN body fragments (just the template). Use "... 2/5 encode_jsxn Encodes raw JSX/TSX source code or HTML into JSXN compact notation (~40% fewer tokens). Use "snippet" mode for JSX fragments (just the template). U... 2/5 read_jsxn Reads a React/Next.js file (.jsx, .tsx, .js, .ts), HTML file (.html), or SVG file (.svg) from disk and returns its JSXN-compressed representation (... 2/5

WRITE TOOLS

write_jsxn Decodes JSXN notation and writes the resulting JSX/TSX or HTML to a file on disk. Creates parent directories if needed. Writes to .jsx/.tsx/.js/.ts... 4/5

// FAQ

How many tools does the Jsx Notation MCP server have? +

The Jsx Notation MCP server exposes 4 tools across 2 categories: Read, Write.

How do I enforce policies on Jsx Notation 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 Jsx Notation server.

What risk categories do Jsx Notation tools fall into? +

Jsx Notation tools are categorised as Read (3), Write (1). Each category has a recommended default policy.

Enforce policies on Jsx Notation

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →