com.latacora/mcp-sdk {:git/url "https://github.com/latacora/mcp-sdk" :git/sha "<latest-commit-sha>"}

(require '[com.latacora.mcp.core :as mcp]) ; for tools, this library provides a convenient way to construct  ; tool specifications using malli schemas for input and output  ; validation (as well as json-schema generation) (def tool (mcp/create-tool-specification {:name "add" :title "Add two numbers" :description "Adds two numbers together" :input-schema [:map [:a int?] [:b int?]] :output-schema [:map [:result int?]] :handler (fn [_exchange {:keys [a b]}] {:result (+ a b)})})) ; when you construct the mcp handler you provide java objects ; like the underlying modelcontextprotocol requests. this means ; you're free to build any of the other mcp server features using ; interop. at a future date we might provide clojure wrappers to ; make constructing them easier, but for now we only provide one for ; tools since they're the most common and tedious to construct with interop. (def handler (mcp/create-ring-handler {:name "hello-world" :version "1.0.0" :tools [tool]})) ; note that this is a custom run-jetty function that preserves ; the original servlet request/response objects in metadata so ; they can be passed to the embedded mcp servlet. it is a drop-in ; replacement for ring.adapter.jetty/run-jetty. here we perform no ; routing and so the mcp server is mounted at the root path, but you ; can embed the handler anywhere in your routing tree. (def server (mcp/run-jetty handler {:port 3000 :join? false}))