Cedarscript File Manipulation

🚀 CEDAR diff MCP Server

A TypeScript-based MCP server implementing CEDARScript, a SQL-like language for code manipulation.

🚀 Quick Start

This is a TypeScript-based MCP server that implements CEDARScript, a SQL-like language for code manipulation. It offers the following capabilities:

• Comprehensive code manipulation syntax.
• Tools for executing CEDARScript operations.
• Support for complex pattern matching and transformation.

✨ Features

Syntax

• SQL-like code manipulation syntax (Data Definition Language, Data Manipulation Language).
• Support for targeting at the file, function, class, and method levels.
• Pattern matching using regular expressions, prefix/suffix rules, and indentation rules.
• Provision of block-level code manipulation functions.

Tools

• edit_file - Execute CEDARScript commands.
  • Accepts scripts and working directories as parameters.
  • Supports file creation, deletion, movement, and updates.
  • Provides pattern-based code transformation capabilities.

🔧 Technical Details

After testing, we found that:

• The command parsing function works properly.
• The syntax supports complex operations.
• The file writing mechanism needs improvement.
• Although a success message is returned, the changes are not persisted.

📦 Installation

Development

Install dependencies:

npm install

Build the server:

npm run build

Use watch for automatic rebuild development:

npm run watch

Usage in Claude Desktop

To use it on Claude Desktop, add the following configuration: On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "cedardiff": {
      "command": "/path/to/cedardiff/build/index.js"
    }
  }
}

📚 Documentation

Debugging

Since the MCP server communicates via standard input and output, debugging can be challenging. We recommend using MCP Inspector, a tool provided as a package script:

npm run inspector

The Inspector will provide a URL to access the debugging tools, which you can open in your browser.

ES Module Migration

The project has migrated to using ES modules. The main changes include:

• Added "type": "module" in package.json.
• Updated tsconfig.json to use "module": "ESNext".
• Converted import/export statements to ES module syntax.
• Updated type definitions to be compatible with ES modules.

Compatibility Notes

• Ensure you are using Node.js version 12 or higher.
• Use import instead of require() for module imports.
• Use the .js extension when importing local files.