Babashka MCP Server

Created By
bmorphisma year ago
A Model Context Protocol server for interacting with Babashka, a native Clojure interpreter for scripting
Overview

What is Babashka MCP Server?

Babashka MCP Server is a Model Context Protocol server designed for interacting with Babashka, a native Clojure interpreter for scripting.

How to use Babashka MCP Server?

To use the Babashka MCP Server, first install Babashka, then install the server dependencies, build the server, and configure it through environment variables. You can execute Babashka code through the server using the provided tools.

Key features of Babashka MCP Server?

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

Use cases of Babashka MCP Server?

  1. Running Clojure scripts in a server environment.
  2. Automating tasks using Babashka's scripting capabilities.
  3. Managing command execution and history in a structured way.

FAQ from Babashka MCP Server?

  • What is Babashka?

Babashka is a native Clojure interpreter for scripting, allowing you to run Clojure code quickly and easily.

  • How do I install Babashka?

You can install Babashka using Homebrew on macOS, a bash script on Linux, or Scoop on Windows.

  • Can I run Babashka scripts without the server?

Yes, Babashka can be run independently without the MCP server for simple scripting tasks.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bmorphism
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

11 hours ago