babashka mcp server

Local 2025-09-01 00:15:13 0
Developer Tools @bmorphism/babashka-mcp-server

Enables execution and management of Babashka scripts using the Model Context Protocol, offering features like caching, command history access, and configurable timeouts for enhanced scripting workflows.

A Model Context Protocol server for interacting with Babashka, a native Clojure interpreter for scripting.

Features

  • Execute Babashka code through MCP tools
  • Cache recent command results
  • Access command history through MCP resources
  • Configurable command timeouts

Prerequisites

Install Babashka

Babashka can be installed in several ways:

macOS

brew install borkdude/brew/babashka

Linux

bash < <(curl -s https://raw.githubusercontent.com/babashka/babashka/master/install)

Windows

# Using scoop
scoop install babashka

For other installation methods, see the official Babashka installation guide.

Verify Installation

After installation, verify Babashka works: 

# Check version
bb --version

# Try a simple expression
bb -e '(+ 1 2 3)'

# Run a script from string
bb -e '(defn hello [x] (str "Hello, " x "!")) (hello "World")'

# Use -i flag to process lines of input
ls | bb -i '(take 2 *input*)'

Installation

# Install dependencies
npm install

# Build the MCP server
npm run build

Configuration

The server can be configured through environment variables:

  • BABASHKA_PATH: Path to the Babashka executable (default: "bb")

Tools

execute

Execute Babashka code with optional timeout:

{
  name: "execute",
  arguments: {
    code: string;      // Babashka code to execute
    timeout?: number;  // Timeout in milliseconds (default: 30000)
  }
}

Example: 

{
  name: "execute",
  arguments: {
    code: "(+ 1 2 3)",
    timeout: 5000
  }
}

Resources

The server maintains a cache of recent command executions accessible through:

  • babashka://commands/{index} - Access specific command results by index

Babashka Language Features

Tail Call Optimization (TCO)

Babashka supports explicit tail call optimization through the recur special form, but does not implement automatic TCO. For example:

;; This will cause stack overflow
(defn countdown [n]
  (if (zero? n)
    :done
    (countdown (dec n))))

;; This works with TCO using recur
(defn countdown [n]
  (if (zero? n)
    :done
    (recur (dec n))))

Useful Resources

Official Resources

Community Tools & Libraries

Development Tools

Development

This server is designed to eventually become self-hosting, meaning it will be rewritten in Babashka itself. The current TypeScript implementation serves as a reference and starting point.

Roadmap

  1. Self-Hosted Implementation
  2. Rewrite the MCP server in Babashka
  3. Leverage Babashka's native capabilities for better performance
  4. Remove Node.js dependency
  5. Maintain full compatibility with MCP protocol

  6. Support all current features:

    • Command execution
    • Resource management
    • Command history
    • Timeout handling

  7. Enhanced Features

  8. Add support for Babashka pods
  9. Implement file watching capabilities
  10. Add REPL integration

  11. Support for multiple Babashka instances

  12. Performance Optimizations

  13. Implement caching strategies
  14. Optimize resource usage

  15. Reduce startup time

  16. Testing & Documentation

  17. Comprehensive test suite
  18. API documentation
  19. Usage examples
  20. Performance benchmarks
[
  {
    "description": "Execute Babashka (bb) code",
    "inputSchema": {
      "properties": {
        "code": {
          "description": "Babashka code to execute",
          "type": "string"
        },
        "timeout": {
          "description": "Timeout in milliseconds (default: 30000)",
          "maximum": 300000,
          "minimum": 1000,
          "type": "number"
        }
      },
      "required": [
        "code"
      ],
      "type": "object"
    },
    "name": "execute"
  }
]