LibraryAI

Created By
YELANDAOKONGa year ago
[C#/AI] (LibraryAI/ConsoleAI) AI 知识库与数据处理程序
Overview

What is LibraryAI?

LibraryAI is an AI knowledge base and data processing program designed to facilitate text chunk processing, vectorization, and search functionalities using a vector database.

How to use LibraryAI?

To use LibraryAI, developers can integrate its core library into their applications, utilize the ConsoleAI for text processing, and connect to vector databases through the MCP framework.

Key features of LibraryAI?

  • Text chunk processing and vectorization for efficient data handling.
  • MCP protocol support for seamless AI integration with vector databases.
  • Debugging tools for testing core library functionalities.

Use cases of LibraryAI?

  1. Implementing AI-driven search functionalities in applications.
  2. Enhancing data processing capabilities in machine learning projects.
  3. Developing applications that require efficient text handling and vector database integration.

FAQ from LibraryAI?

  • What programming language is LibraryAI built with?

LibraryAI is developed using C#.

  • Is LibraryAI suitable for production use?

LibraryAI is in the early stages of development and may require further testing before production use.

  • How can I contribute to LibraryAI?

Contributions can be made through the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
YELANDAOKONG
Star
0
Language
C#
License
-
Tags

Recommend Servers

View All
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)

a day ago