Knowledge Base MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Knowledge Base MCP Server?

The Knowledge Base MCP Server is a tool designed to list and retrieve content from various knowledge bases, enabling efficient access to information.

how to use Knowledge Base MCP Server?

To use the Knowledge Base MCP Server, clone the repository, install dependencies, configure environment variables, build the server, and add it to the MCP settings. You can then use the provided tools through the MCP interface.

key features of Knowledge Base MCP Server?

  • Lists available knowledge bases.
  • Retrieves similar chunks from the knowledge base based on a query.
  • Supports semantic search using a FAISS index.

use cases of Knowledge Base MCP Server?

  1. Accessing company knowledge bases for employee onboarding.
  2. Retrieving IT support documentation quickly.
  3. Searching through various knowledge bases for relevant information.

FAQ from Knowledge Base MCP Server?

  • What are the prerequisites for running the server?

You need Node.js (version 16 or higher) and npm installed on your system.

  • How does the server handle knowledge base updates?

The server automatically updates the FAISS index when it starts or when files in the knowledge base are modified.

  • Can I customize the Hugging Face model used?

Yes, you can specify the Hugging Face model name through an environment variable.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
Unlicense 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