Source Library

Created By
Embassy of the Free Mind5 months ago
Search and cite 500+ translated historical texts (alchemy, Hermeticism, Renaissance) with DOI-backed academic citations. Access rare Latin and German manuscripts from the 15th-18th centuries.
Overview

What is Source Library?

Source Library is a digital platform that allows users to search and cite over 500 translated historical texts, including rare Latin and German manuscripts from the 15th to 18th centuries, with DOI-backed academic citations.

How to use Source Library?

To use Source Library, you can access the platform via its website or GitHub repository, where you can utilize tools to search for texts, get quotes with citations, and access detailed book information.

Key features of Source Library?

  • Search through 500+ translated historical texts.
  • Obtain formatted citations (inline, footnote, DOI URL) for quotes.
  • Access metadata and AI-generated summaries for texts.

Use cases of Source Library?

  1. Researchers can find and cite historical texts for academic papers.
  2. Students can access rare manuscripts for study and reference.
  3. Historians can explore topics related to alchemy, Hermeticism, and Renaissance philosophy.

FAQ from Source Library?

  • Can I access all texts for free?

Yes! Source Library provides free access to its collection of texts.

  • How do I cite a text from Source Library?

You can get formatted citations directly from the platform when you retrieve a quote.

  • What types of texts are available?

The library includes texts on alchemy, Hermeticism, Neoplatonism, Rosicrucianism, and more.

Server Config

{
  "mcpServers": {
    "source-library": {
      "command": "npx",
      "args": [
        "-y",
        "@source-library/mcp-server"
      ]
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
Embassy of the Free Mind
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
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)

19 hours ago