Babashka MCP Server

Name: Babashka MCP Server
Author: MCP-Mirror

@MCP-Mirror

リポジトリ

Babashka MCP Server について

Mirror of

#babashka #mcp-server #clojure

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

MCP-Mirror

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Babashka MCP Server?

A Model Context Protocol server for interacting with Babashka, a native Clojure interpreter for scripting. It allows AI assistants to execute Babashka code and access command history through MCP tools and resources.

How to use Babashka MCP Server?

Install Babashka (prerequisite), then run npm install and npm run build from the server directory. Configure with the BABASHKA_PATH environment variable (default "bb"). Use the execute tool to run Babashka code with an optional timeout (default 30000 ms), and access cached results via babashka://commands/{index} resource URIs.

Key features of Babashka MCP Server

Execute Babashka code through MCP tools
Cache recent command results
Access command history as MCP resources
Configurable command timeouts (default 30 seconds)

Use cases of Babashka MCP Server

Run Clojure snippets within AI assistant conversations
Automate Babashka script execution from chat interfaces
Inspect and reuse previous command outputs via resource URIs
Provide a REPL-like interaction with Babashka from any MCP client

FAQ from Babashka MCP Server

What dependencies are required?

Babashka must be installed system‑wide (via Homebrew, scoop, or the official install script). The server itself requires Node.js and npm to build.

How do I configure the Babashka executable path?

Set the BABASHKA_PATH environment variable to the full path of the Babashka binary. The default is "bb".

What tools and resources does the server expose?

One tool (execute) accepts Babashka code and an optional timeout. One resource pattern (babashka://commands/{index}) allows access to previously executed command results.

Does Babashka support tail‑call optimization?

Babashka supports explicit TCO via the recur special form but does not implement automatic tail‑call optimization.

What is the future plan for this server?

The project aims to rewrite the server in Babashka itself (removing the Node.js dependency) and to add support for Babashka pods, file watching, REPL integration, and multiple instances.