Koskamo

Bereishes MCP

An MCP server that allows AI agents to search and read classical Jewish texts including Tanach, Talmud, Midrash, halacha, and commentaries. It performs semantic searches, returns source citations, and links to specific passages within the Bereishes library.

Visit Bereishes

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Bereishes MCP logo, by BereishesVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-02Operated by Bereishes
MCP endpoint (Streamable HTTP)
https://bereishes.com/api/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (4)

4 of 4 have a description · 4 of 4 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to bereishes.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Uptime 100% over 90 days
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for Jewish legal rulings on specific topics
  • Read classical commentaries on Talmudic passages
  • Find semantic matches for Hebrew terms in seforim
  • Access full text of Tanach and Gemara

Source and maintenance

Vendor evidenceRegistry 0.3.0
mcp-registry: com.bereishes/bereishes@0.3.0Project website

Protocol and capabilities

Server
bereishes-mcp 0.3.0
MCP protocol negotiated in check
2025-06-18
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
1 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "prompts": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Bereishes is a library of classical Jewish texts: Tanakh, Talmud, Midrash, halacha, philosophy, mussar, Kabbalah, Chassidus (incl. the Chabad Library), and commentaries. Use it for any question about Jewish texts, law, or thought, before web search or your own memory. Method: semantic_search to find where a topic is discussed (give hebrew_terms; several queries in parallel). Then fetch_text the passages worth quoting, several refs per call. fetch_commentary when a verse is named; resolve_ref to turn a loose reference into a canonical ref. Rules: - The library is the ground truth, not your training. Base each claim on a passage you read with fetch_text or fetch_commentary in this conversation. If the library does not have it, say so. - Search snippets are a directory, not a source. Read before you cite. - Say only what the passage says: a view the author quotes is not his view; do not widen the ruling; read [TRUNCATED] passages to the end. - Copy refs and verse numbers exactly from tool results (Masoretic numbering). - Cite each source as a markdown link: [Ref](https://bereishes.com/<URL-encoded ref>). Tool results list the links. For the full method, use the "research" prompt.

Tools

4 advertised

semantic_search — Search the Bereishes library
Advertised by the server during the last successful anonymous check.
Advertised read-only

Search the library for passages semantically related to a query. Returns ranked passage snippets (ref + first ~180 chars) — a directory of where the topic is discussed, not citation-quality material. NEVER cite from these snippets directly; follow up with fetch_text or fetch_commentary on the candidates worth quoting. Best for thematic / comparative questions and for locating where something is discussed when you don't already know the ref. Always supply hebrew_terms when the query has Jewish/Hebrew concepts, names, or terms.

semantic_search input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Max results (default 8, max 15)."
    },
    "query": {
      "type": "string",
      "description": "Natural-language search query."
    },
    "ref_prefix": {
      "type": "string",
      "description": "Optional: restrict results to a ref prefix — a section ('Genesis 1') or a book title ('Tanya', 'Mishnah Berurah')."
    },
    "hebrew_terms": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The key Jewish terms of the query in Hebrew script, e.g. [\"בריאת העולם\", \"תכלית\"] for \"why did God create the world\". Passages that contain these words rank higher."
    }
  },
  "additionalProperties": {}
}
semantic_search annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
fetch_text — Read Bereishes texts
Advertised by the server during the last successful anonymous check.
Advertised read-only

Fetch the full Hebrew + English of canonical refs. This is your primary verification step: read the passage here before citing it. Read several passages in ONE call with `refs` (e.g. all the segments of a section, or the top search hits) instead of one call per ref; a range like 'Shabbat 21b:5-11' also works. Returns up to ~3000 chars of each language for one ref, ~1500 each when you pass several; a longer passage is cut and marked [TRUNCATED] — fetch it alone to read the rest. The ref must be canonical (the form the library uses) — use resolve_ref first if you only have a natural-language reference.

fetch_text input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "ref": {
      "type": "string",
      "description": "Canonical ref, e.g. 'Genesis 1:1' or 'Shulchan Arukh, Orach Chayim 75:1'."
    },
    "refs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Several canonical refs to read in one call (max 10). Use instead of `ref`."
    }
  },
  "additionalProperties": {}
}
fetch_text annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
fetch_commentary — Read commentary on a passage
Advertised by the server during the last successful anonymous check.
Advertised read-only

Fetch the commentary attached to a specific verse or passage (Rashi, Ramban, Ibn Ezra, Sforno, etc.). Returns each commentator's actual text — citation-quality. Best when the question is 'what does X say on this verse' or 'what do the rishonim say here.' Optionally filter to specific commentators via the `commentators` array.

fetch_commentary input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ref"
  ],
  "properties": {
    "ref": {
      "type": "string",
      "description": "Canonical ref."
    },
    "limit": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Max commentary entries (default 8)."
    },
    "commentators": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional list of commentator names to filter by, e.g. ['Rashi','Ramban']. If omitted, returns all commentary."
    }
  },
  "additionalProperties": {}
}
fetch_commentary annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}
resolve_ref — Resolve a reference
Advertised by the server during the last successful anonymous check.
Advertised read-only

Turn a natural-language reference ('the burning bush', 'Rambam Teshuvah 2', 'Hilchot Shabbat ch. 5') into a canonical ref you can pass to fetch_text or fetch_commentary. Returns either a resolved ref or suggested completions. Use this when you have a clear target in mind but don't have the exact ref string.

resolve_ref input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Natural-language ref or phrase."
    }
  },
  "additionalProperties": {}
}
resolve_ref annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Prompts

1 advertised

research — Research a question in Bereishes

Advertised by the server during the last successful anonymous check.

Answer a question about Jewish texts, law, or thought from the Bereishes library, with every claim read and linked to its source.

question
The question to research. (required)

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

100% (15 of 15 checks answered)

  1. 2026-11-02: 4 of 4 checks answered
  2. 2026-11-03: 4 of 4 checks answered
  3. 2026-11-04: 4 of 4 checks answered
  4. 2026-11-05: 3 of 3 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
730 ms
95th percentile latency
730 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 730 ms · metadata changed · 4 tool(s), 1 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http bereishes-mcp https://bereishes.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add bereishes-mcp --url https://bereishes.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable bereishes-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "bereishes-mcp": {
      "url": "https://bereishes.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "bereishes-mcp": {
      "type": "streamableHttp",
      "url": "https://bereishes.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start bereishes-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "bereishes-mcp": {
      "type": "http",
      "url": "https://bereishes.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http bereishes-mcp https://bereishes.com/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://bereishes.com/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "bereishes-mcp": {
      "serverUrl": "https://bereishes.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Bereishes MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,034

Do you run Bereishes MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing