Babashka MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Babashka MCP Server?

Babashka MCP Server is a Model Context Protocol server designed for executing Babashka code, which is 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 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. Caching and managing command executions for efficient resource usage.

FAQ from Babashka MCP Server?

  • What is Babashka?

Babashka is a native Clojure interpreter for scripting that allows you to run Clojure code quickly and efficiently.

  • How do I install Babashka?

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

  • Can I configure the server?

Yes! The server can be configured through environment variables, including the path to the Babashka executable.

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago