v0.3.0

Features

• Add BUN_BE_BUN support for direct npm package execution (#3)

What's New: You can now run npm packages directly without redundant bunx calls:

# Before (redundant bunx):
bunx mcp-controller bunx @modelcontextprotocol/server-filesystem /path

# Now (clean UX):
bunx mcp-controller @modelcontextprotocol/server-filesystem /path

The controller automatically detects npm packages and uses the appropriate execution method, making the user experience much cleaner while maintaining full backward compatibility.

v0.2.0: Wildcard Tool Filtering

What's New in v0.2.0

🌟 Wildcard Tool Filtering

• Added support for wildcard patterns in tool filtering using * character
• Extend --enabled-tools and --disabled-tools to support glob-like patterns
• Full backward compatibility with exact tool name matching

Usage Examples

# Enable tools matching wildcard patterns
mcp-controller --enabled-tools "get_*,list_*" bun run server.ts

# Disable dangerous tools with wildcard
mcp-controller --disabled-tools "dangerous_*" bun run server.ts

# Mix exact and wildcard patterns
mcp-controller --enabled-tools "add,get_*" bun run server.ts

# List tools with wildcard filtering
mcp-controller list-tools --enabled-tools "*_log" bun run server.ts

Features

• ✨ Wildcard pattern matching with * character
• 🔄 Backward compatible with exact tool names
• 📝 Enhanced help text with wildcard usage examples
• 🧪 Comprehensive test coverage for wildcard scenarios
• 🏗️ Improved test infrastructure with shared utilities

Technical Improvements

• Added matchesToolPattern() utility function with proper regex escaping
• Refactored test suite with reusable helper functions
• Enhanced MCP protocol compliance and validation

Full Changelog: v0.1.1...v0.2.0