Brain Server - MCP Knowledge Embedding Service

Created By
patrickdelucaa year ago
Overview

what is Brain Server?

Brain Server is a powerful MCP (Model Context Protocol) server designed for managing knowledge embeddings and performing vector searches.

how to use Brain Server?

To use Brain Server, clone the repository, install the dependencies, configure the environment variables, and start the server in either development or production mode.

key features of Brain Server?

  • High-quality vector embeddings for knowledge content
  • Semantic search capabilities to find knowledge based on meaning
  • Compliance with Model Context Protocol for AI integration
  • Organization of knowledge into domain-specific brains
  • Context-aware retrieval for enhanced understanding
  • Real-time progress tracking of long-running operations

use cases of Brain Server?

  1. Managing and retrieving knowledge in AI applications
  2. Enhancing search functionalities in knowledge management systems
  3. Organizing domain-specific knowledge for better accessibility

FAQ from Brain Server?

  • What is MCP?

MCP stands for Model Context Protocol, which is a framework for integrating AI models with knowledge management systems.

  • How do I install Brain Server?

You can install Brain Server by cloning the repository and following the installation instructions provided in the documentation.

  • Can I contribute to Brain Server?

Yes! Contributions are welcome, and you can submit a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
patrickdeluca
Star
0
Language
TypeScript
License
-

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