Sefaria Jewish Library MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Sefaria Jewish Library MCP Server?

Sefaria Jewish Library MCP Server is an MCP (Model Context Protocol) server that provides access to Jewish texts from the Sefaria library, enabling Large Language Models to retrieve and reference these texts through a standardized interface.

How to use Sefaria Jewish Library MCP Server?

To use the server, clone the repository from GitHub, navigate to the directory, and run the server using the provided commands. It can also be accessed through an MCP client that supports the Model Context Protocol.

Key features of Sefaria Jewish Library MCP Server?

  • Retrieve Jewish texts by reference.
  • Retrieve commentaries on a given text.

Use cases of Sefaria Jewish Library MCP Server?

  1. Accessing specific Jewish texts for study or research.
  2. Retrieving commentaries to enhance understanding of the texts.
  3. Integrating with AI applications for educational purposes.

FAQ from Sefaria Jewish Library MCP Server?

  • What programming language is required to run the server?

Python 3.10 or higher is required to run the server.

  • Can I run the server on my local machine?

Yes, you can run the server locally by following the installation instructions provided in the documentation.

  • Is there any support for using this server with AI models?

Yes, the server is designed to work with Large Language Models through the Model Context Protocol.

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.

21 hours ago