FluffOS MCP Server
Real driver validation for LPC development - An MCP server that wraps FluffOS CLI tools to provide actual driver-level validation and debugging.
This MCP server exposes FluffOS's powerful CLI utilities (symbol and lpcc) to AI assistants, enabling them to validate LPC code against the actual driver and examine compiled bytecode.
What This Enables
⨠AI assistants can now:
Validate LPC files using the actual FluffOS driver (not just syntax checking)
Catch runtime compilation issues that static analysis misses
Examine compiled bytecode to debug performance or behavior issues
Understand how LPC code actually compiles
Tools
š
fluffos_validate: Validate an LPC file using FluffOS'ssymboltoolš¬
fluffos_disassemble: Disassemble LPC to bytecode usinglpcc
Prerequisites
1. FluffOS Installation
You need FluffOS installed with the CLI tools available. The following binaries should exist:
symbol- For validating LPC fileslpcc- For disassembling to bytecode
2. Node.js
Node.js 16+ required:
3. Install Dependencies
Configuration
The server requires two environment variables:
FLUFFOS_BIN_DIR- Directory containing FluffOS binaries (symbol,lpcc)MUD_RUNTIME_CONFIG- Path to your FluffOS config file (e.g.,/mud/lib/etc/config.test)
Setup for Different AI Tools
Warp (Terminal)
Add to your Warp MCP configuration:
Location: Settings ā AI ā Model Context Protocol
Important: Use absolute paths!
Restart Warp after adding the configuration.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or equivalent:
Restart Claude Desktop after configuration.
Usage Examples
Once configured, you can ask your AI assistant:
"Validate this LPC file with the actual driver"
ā AI uses fluffos_validate to run symbol
"Show me the bytecode for this function"
ā AI uses fluffos_disassemble to run lpcc
"Why is this code slow?" ā AI examines the disassembly to identify inefficient patterns
How It Works
AI assistant sends MCP tool requests
Server spawns appropriate FluffOS CLI tool
CLI tool validates/disassembles using the driver
Server returns results to AI
AI understands your code at the driver level!
Complementary Tools
This server works great alongside:
lpc-mcp - Language server integration for code intelligence
VS Code with jlchmura's LPC extension - IDE support
Use them together for the complete LPC development experience!
Contributing
PRs welcome! This is a simple wrapper that can be extended with more FluffOS tools.
Credits
FluffOS Team - For the amazing driver and CLI tools
Model Context Protocol - Making this integration possible
License
Unlicense - Public Domain. Do whatever you want with this code.
local-only server
The server can only run on the client's local machine because it depends on local resources.
Enables AI assistants to validate LPC code and examine compiled bytecode using FluffOS driver tools, providing real driver-level compilation checking and performance analysis for MUD development.